Triple
T24791614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GTP |
E620265
|
entity |
| Predicate | regulationNameInWEC |
P109347
|
FINISHED |
| Object | Le Mans Daytona h |
—
|
NE NERFINISHED |
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: Le Mans Daytona h | Statement: [GTP, regulationNameInWEC, Le Mans Daytona h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulationNameInWEC Context triple: [GTP, regulationNameInWEC, Le Mans Daytona h]
-
A.
regulationName
chosen
Indicates the specific name or title assigned to a regulation that governs or constrains something.
-
B.
regulationAtIssue
Indicates that a specific regulation is the subject of concern, dispute, or analysis in the given context.
-
C.
worksOnRegulationType
Indicates that an entity is involved in work or activities related to a specific type or category of regulation.
-
D.
regulatesOrIsRegulatedBy
Indicates a bidirectional regulatory relationship in which one entity controls, influences, or modulates another, or is itself controlled, influenced, or modulated by that other entity.
-
E.
regulatesIn
Indicates that one entity controls, modulates, or influences the activity, expression, or behavior of another entity within a system or process.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 4:47 a.m.