Triple
T35758329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hockenheimring |
E1033504
|
entity |
| Predicate | reprofiledBy |
P70830
|
FINISHED |
| Object | Hermann Tilke |
—
|
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: Hermann Tilke | Statement: [Hockenheimring, reprofiledBy, Hermann Tilke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reprofiledBy Context triple: [Hockenheimring, reprofiledBy, Hermann Tilke]
-
A.
reprogrammedBy
Indicates that an entity’s original programming or code has been altered or replaced by another specified agent or process.
-
B.
reworkedBy
chosen
Indicates that an existing work, product, or result has been modified, revised, or substantially altered by a particular agent.
-
C.
reconfiguredFrom
Indicates that one entity has been altered, adapted, or rearranged from a prior entity or configuration, such that the current form results from modifying the original.
-
D.
reclassifiedBy
Indicates that an entity’s classification or category has been changed by a specific agent or authority.
-
E.
reassignedFrom
Indicates that an entity previously held by or associated with one source has been transferred or moved away from that original source to another.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1c2030881908aeb62c4eba771d7 |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.