Triple
T3657802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renault–Gitane |
E77574
|
entity |
| Predicate | teamStrategy |
P31887
|
FINISHED |
| Object | building around a single designated leader for Grand Tours |
—
|
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: building around a single designated leader for Grand Tours | Statement: [Renault–Gitane, teamStrategy, building around a single designated leader for Grand Tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamStrategy Context triple: [Renault–Gitane, teamStrategy, building around a single designated leader for Grand Tours]
-
A.
strategyType
chosen
Indicates the specific kind or category of strategy associated with an entity or action.
-
B.
defensivePlan
Indicates a relationship where an entity formulates or adopts a strategy specifically intended to protect against threats, attacks, or other adverse actions.
-
C.
coachingTeam
Indicates that one entity serves as a coach or coaching staff for a particular team.
-
D.
opponentStrategy
Indicates that one entity employs or represents a strategic plan specifically designed to counter or compete against another entity.
-
E.
teamSelection
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d36c1c8190920397a75de4c47d |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.