Triple
T27357952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avatar 4 |
E685737
|
entity |
| Predicate | featuresFictionalPlanet |
P76995
|
FINISHED |
| Object | Pandora |
—
|
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: Pandora | Statement: [Avatar 4, featuresFictionalPlanet, Pandora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFictionalPlanet Context triple: [Avatar 4, featuresFictionalPlanet, Pandora]
-
A.
fictionalPlanet
Indicates that the subject is a planet that exists only in fiction or imagination, not in the real universe.
-
B.
featuresUniverse
chosen
Indicates that one entity includes, presents, or prominently showcases a particular universe or world as part of its content or structure.
-
C.
fictionalUniverseLocation
Indicates that one entity is a location or setting within the fictional universe to which the other entity belongs or in which it takes place.
-
D.
notableLocationOnHomeworld
Indicates that a specific location is notable or significant on the entity’s homeworld.
-
E.
homeworldType
Indicates the type or classification of a subject’s homeworld (e.g., planet, moon, habitat) in relation to that subject.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 27, 2026, 11:52 a.m.