Triple
T15951919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGV V150 |
E386837
|
entity |
| Predicate | trackCondition |
P78490
|
FINISHED |
| Object | specially prepared track |
—
|
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: specially prepared track | Statement: [TGV V150, trackCondition, specially prepared track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackCondition Context triple: [TGV V150, trackCondition, specially prepared track]
-
A.
hasRoadCondition
chosen
Indicates that a specified road segment possesses or is characterized by a particular condition or state (e.g., quality, surface, or status).
-
B.
navigationCondition
Indicates the specific circumstances or requirements that must be satisfied for a navigation action or route to be valid or taken.
-
C.
transmissionCondition
Indicates the circumstances or requirements under which something is transmitted from one entity to another.
-
D.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
-
E.
ballCondition
Indicates the specific state or status a ball is in, such as its physical condition, readiness for use, or compliance with required standards.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.