Triple
T20267340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G3 |
E499002
|
entity |
| Predicate | hasRotatingLineup |
P139469
|
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: [G3, hasRotatingLineup, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRotatingLineup Context triple: [G3, hasRotatingLineup, true]
-
A.
lineupChange
Indicates a modification in the composition or order of participants in a lineup, such as adding, removing, or rearranging members.
-
B.
replacedInLineupBy
Indicates that one participant in a lineup is substituted or superseded by another participant in that same lineup.
-
C.
usesCrewRotationWith
Indicates that one entity applies a crew rotation system or schedule in conjunction with another entity.
-
D.
notableLineup
Indicates that an entity is recognized as part of a particularly significant or distinguished group, roster, or cast associated with another entity.
-
E.
hasRetiredPlayersFrom
Indicates that an entity has players who previously played for it and have since retired, originating from the specified source entity (e.g., team, league, or country).
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674d001f081908910eedd262ae13a |
completed | April 20, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:42 p.m.