Triple
T34696406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Princess of Mars |
E891042
|
entity |
| Predicate | fictionalPlanetName |
P133723
|
FINISHED |
| Object | Barsoom |
—
|
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: Barsoom | Statement: [A Princess of Mars, fictionalPlanetName, Barsoom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalPlanetName Context triple: [A Princess of Mars, fictionalPlanetName, Barsoom]
-
A.
fictionalPlanet
chosen
Indicates that the subject is a planet that exists only in fiction or imagination, not in the real universe.
-
B.
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.
-
C.
fictionalPlaceType
Indicates that a place is a fictional location and specifies what type or category of fictional place it is.
-
D.
fictionalGalaxy
Indicates that something exists within, originates from, or is associated with a galaxy that is imaginary or not part of the real universe.
-
E.
fictionalSanctuaryName
Indicates that an entity has a designated name used for a fictional sanctuary or refuge.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 1, 2026, 2:05 a.m.