Triple
T7463388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby Racer |
E176306
|
entity |
| Predicate | isOperatedIn |
P77263
|
FINISHED |
| Object | amusement parks |
—
|
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: amusement parks | Statement: [Derby Racer, isOperatedIn, amusement parks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOperatedIn Context triple: [Derby Racer, isOperatedIn, amusement parks]
-
A.
mayBeOperatedBy
Indicates that an entity has the potential or permission to be operated, controlled, or run by another entity.
-
B.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
C.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
D.
operatedThrough
Indicates that an action, process, or influence is carried out or mediated via a particular intermediary, channel, or mechanism.
-
E.
operatedWith
Indicates that an entity performed an action, function, or process using a specified tool, method, or instrument.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d9d25c819087efc772b5b127fa |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f386daac81908ded91b397b44148 |
completed | March 27, 2026, 9:15 p.m. |
Created at: March 27, 2026, 3:39 p.m.