Triple
T6047989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Cubs |
E134714
|
entity |
| Predicate | parentLeagueSystem |
P8322
|
FINISHED |
| Object | Major League Baseball farm system |
—
|
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: Major League Baseball farm system | Statement: [Iowa Cubs, parentLeagueSystem, Major League Baseball farm system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentLeagueSystem Context triple: [Iowa Cubs, parentLeagueSystem, Major League Baseball farm system]
-
A.
parentLeagueStatus
Indicates the status or condition of a league in relation to its parent league or overarching league structure.
-
B.
fatherLeague
Indicates that an entity serves as the primary or parent league from which another league is derived or governed.
-
C.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
D.
typeOfLeagueSystem
chosen
Indicates that one entity is the kind or structure of league system to which another entity belongs or in which it operates.
-
E.
hasSeparateLeagueSystemFor
Indicates that one entity organizes or maintains a distinct, independent league structure specifically for another entity or group.
- 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056e70fd48190b4554e9a516a1c88 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.