Triple
T1342269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippodrome Circus |
E28490
|
entity |
| Predicate | hasSpecialEffect |
P8792
|
FINISHED |
| Object | floodable ring |
—
|
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: floodable ring | Statement: [Hippodrome Circus, hasSpecialEffect, floodable ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialEffect Context triple: [Hippodrome Circus, hasSpecialEffect, floodable ring]
-
A.
specialEffectsBy
Indicates that the special effects for something (such as a film, scene, or shot) are created or provided by a particular person or entity.
-
B.
notableEffect
Indicates that one entity has a significant impact, consequence, or influence on another entity or situation.
-
C.
hasSpecialUnit
Indicates that an entity possesses or is associated with a distinct, designated unit that has a special role, function, or status.
-
D.
hasSpecialProcedure
Indicates that a particular entity is associated with or governed by a designated special procedure or process.
-
E.
involvedPhysicalEffect
chosen
Indicates that one entity participates in causing, experiencing, or mediating a physical effect on another entity or the environment.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c2174d048190a6e9380df302265f |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.