Triple
T19761094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phantom’s Revenge |
E474628
|
entity |
| Predicate | loopsRemoved |
P137221
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Phantom’s Revenge, loopsRemoved, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loopsRemoved Context triple: [Phantom’s Revenge, loopsRemoved, 4]
-
A.
loopsTo
Indicates that an entity has a path or connection that starts and ends at the same point, forming a loop back to itself.
-
B.
loopsFrom
Indicates that a path, process, or connection starts at a given point and returns back to that same point, forming a loop.
-
C.
loopLocation
Indicates the specific place or context in which a loop occurs or is situated.
-
D.
laterRemovedTo
Indicates that an entity was moved or transferred to a location or state at a later time, after an earlier condition or placement.
-
E.
loopType
Indicates the specific kind or category of loop structure or iteration pattern used in a process or control flow.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6531f38b48190b1663870a8da5a59 |
completed | April 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:48 p.m.