Triple
T31433790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson City Cardinals |
E801867
|
entity |
| Predicate | operatedAsCardinalsAffiliateFrom |
P154045
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [Johnson City Cardinals, operatedAsCardinalsAffiliateFrom, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsCardinalsAffiliateFrom Context triple: [Johnson City Cardinals, operatedAsCardinalsAffiliateFrom, 1975]
-
A.
operatedAsGiantsAffiliateUntil
Indicates that an entity functioned as an affiliate of the Giants organization up to a specified time.
-
B.
operatedAsAffiliateFrom
chosen
Indicates that one entity functioned as an affiliate of another entity starting from a specified point in time.
-
C.
cardinalsFranchise
Indicates that an entity is the sports franchise known as the Cardinals associated with a particular league, city, or organization.
-
D.
cardinalsLeague
Indicates that a particular league is the league in which the Cardinals team competes or is affiliated.
-
E.
cardinalsDivision
Indicates that one entity is a divisional grouping or classification within a larger organizational or competitive structure associated with cardinals.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
Created at: April 30, 2026, 8:59 p.m.