Triple
T32094073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha Jubilo |
E819678
|
entity |
| Predicate | hasCorporateTeamOrigin |
P204267
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Yamaha Jubilo, hasCorporateTeamOrigin, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorporateTeamOrigin Context triple: [Yamaha Jubilo, hasCorporateTeamOrigin, true]
-
A.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
B.
corporateTeamOf
Indicates that one entity is a member of, or belongs to, the same corporate team or organizational unit as another entity.
-
C.
hasCorporateGroup
Indicates that one corporate entity belongs to, or is associated with, a broader corporate group or conglomerate.
-
D.
isEarlyTeamOf
Indicates that one entity was part of the initial or founding group associated with another entity, before later members or teams joined.
-
E.
hasFactoryTeam
Indicates that an entity has an officially supported or owned team directly operated by the manufacturer or producer.
- F. None of above. chosen
Provenance (4 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a035b78140081908e451cb63d3c1c7c |
completed | May 12, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_6a035af3d8f48190bf1f3741d374404e |
completed | May 12, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_6a035b773898819099125a5efc239d3e |
completed | May 12, 2026, 4:55 p.m. |
Created at: May 1, 2026, 12:25 a.m.