Triple
T35244642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyoda family |
E1017623
|
entity |
| Predicate | memberAssociatedWith |
P10953
|
FINISHED |
| Object | Keidanren |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Keidanren | Statement: [Toyoda family, memberAssociatedWith, Keidanren]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberAssociatedWith Context triple: [Toyoda family, memberAssociatedWith, Keidanren]
-
A.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
-
B.
membershipRecordedBy
Indicates that the recording or documentation of a membership was carried out or created by a specific agent or system.
-
C.
hasAssociateMember
chosen
Indicates that an entity has another entity connected to it in a non-full, typically limited or secondary, membership capacity.
-
D.
affiliateOfType
Indicates that an affiliate entity belongs to, or is categorized under, a specific type or classification.
-
E.
membershipIndicatedBy
Indicates that an entity’s membership in a group, set, or organization is evidenced, signaled, or made known by another entity or attribute.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 3, 2026, 4:02 p.m.