Triple
T19694959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Watchers |
E472931
|
entity |
| Predicate | fictionalWorldElement |
P116836
|
FINISHED |
| Object | Martian colonists |
—
|
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: Martian colonists | Statement: [The Watchers, fictionalWorldElement, Martian colonists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalWorldElement Context triple: [The Watchers, fictionalWorldElement, Martian colonists]
-
A.
fictionalPlaceType
Indicates that a place is a fictional location and specifies what type or category of fictional place it is.
-
B.
hasFictionalSettingElement
chosen
Indicates that something includes or is associated with a specific element or component of a fictional setting.
-
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.
basedInFictionalSetting
Indicates that an entity’s primary location or setting exists within a fictional or imaginary world rather than the real world.
-
E.
fictionalUniverse
Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6421385e88190b22b12ab3d851dea |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.