Triple
T243285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College Football Playoff |
E4979
|
entity |
| Predicate | selectionCommitteeSize |
P9733
|
FINISHED |
| Object | 13 members |
—
|
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: 13 members | Statement: [College Football Playoff, selectionCommitteeSize, 13 members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionCommitteeSize Context triple: [College Football Playoff, selectionCommitteeSize, 13 members]
-
A.
establishesCommittee
Indicates that an entity formally creates or sets up a committee, typically assigning it a specific purpose or function.
-
B.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
-
C.
hasNumberOfCouncillors
Indicates the relationship that specifies how many councillors are associated with a given entity.
-
D.
delegateCountWinner
Indicates that the referenced entity is the candidate or option that has secured the highest number of delegates in a given selection or election process.
-
E.
membersAreElectedIn
Indicates that the members of a group or body attain their positions through an election process held within a specified context or jurisdiction.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b62839c8190824064fe5da6a92a |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25dcba5148190ab80fd14c7cf4bb4 |
completed | Feb. 28, 2026, 3:15 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.