Triple
T32720981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avatar 5 |
E836671
|
entity |
| Predicate | mainSettingName |
P139583
|
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 5, mainSettingName, Pandora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSettingName Context triple: [Avatar 5, mainSettingName, Pandora]
-
A.
knownAsSettingFor
Indicates that something is recognized or regarded as the typical or notable setting or backdrop for something else.
-
B.
standardSettingFor
Indicates that one entity establishes or defines the norms, criteria, or benchmarks that another entity is expected to follow or be measured against.
-
C.
mainSettingPeriod
Indicates the historical or temporal period in which the primary setting of a work or event takes place.
-
D.
indicatedSetting
chosen
Indicates that one entity specifies, denotes, or points out a particular setting or configuration associated with another entity.
-
E.
notableSetting
Indicates that a particular place or environment is especially significant or prominent as the context in which an entity is situated or occurs.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 1:11 a.m.