Triple
T30056833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superman television series |
E763754
|
entity |
| Predicate | featuresLocationFrom |
P7690
|
FINISHED |
| Object | Krypton |
—
|
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: Krypton | Statement: [Superman television series, featuresLocationFrom, Krypton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresLocationFrom Context triple: [Superman television series, featuresLocationFrom, Krypton]
-
A.
featuresLocation
chosen
Indicates that something is characterized by or includes a specific location as one of its notable attributes.
-
B.
featuresPosition
Indicates that one entity specifies or defines the spatial or ordered position of another entity.
-
C.
mapLocation
Indicates a relationship where an entity is associated with a specific position or area on a map.
-
D.
locates
Indicates that one entity determines, specifies, or identifies the position or place of another entity in space or within a given context.
-
E.
featuresCollectionFrom
Indicates that one entity serves as the source or origin from which a collection of features is derived or obtained for another entity.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: April 29, 2026, 6:56 p.m.