Triple
T1245648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nippon Professional Baseball |
E26758
|
entity |
| Predicate | ballCompositionStandardized |
P8601
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Nippon Professional Baseball, ballCompositionStandardized, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballCompositionStandardized Context triple: [Nippon Professional Baseball, ballCompositionStandardized, 2011]
-
A.
ballType
Indicates the specific category or kind of ball associated with an entity.
-
B.
standardComposition
chosen
Indicates that one entity is composed or constructed according to a recognized or conventional standard defined by another entity.
-
C.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
D.
specialComposition
Indicates that one entity is composed of another in a distinctive or non-standard way, highlighting a particular or exceptional form of composition between them.
-
E.
constitutedBy
Indicates that something is made up of, composed from, or formed by the specified parts or elements.
- 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf65c41c8190b4c65e015d1264c0 |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb696a38819095845c84f0241287 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.