Triple
T15922288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open de France |
E386120
|
entity |
| Predicate | recordToPar |
P120549
|
FINISHED |
| Object | −21 |
—
|
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: −21 | Statement: [Open de France, recordToPar, −21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordToPar Context triple: [Open de France, recordToPar, −21]
-
A.
recordProducer
Indicates that one entity serves as the producer responsible for creating or overseeing the production of a recorded work associated with another entity.
-
B.
recordsType
Indicates that one entity documents, stores, or keeps an official account of a particular type or category of information, event, or item.
-
C.
recordStatus
Indicates the current state or condition of a record within a system or process (e.g., active, inactive, pending, or archived).
-
D.
recordKeeper
Indicates a relationship where one entity is responsible for maintaining, managing, or preserving official records or documented information about another entity or activity.
-
E.
recordStructure
Indicates a relationship where an entity defines, organizes, or specifies the internal layout and components of a record or data structure.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e172b213e481909ee0c05e16229a26 |
completed | April 16, 2026, 11:37 p.m. |
Created at: April 10, 2026, 4:52 a.m.