Triple
T31106913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outpost 32 |
E792817
|
entity |
| Predicate | designationInCanon |
P86766
|
FINISHED |
| Object | Outpost 32 |
—
|
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: Outpost 32 | Statement: [Outpost 32, designationInCanon, Outpost 32]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designationInCanon Context triple: [Outpost 32, designationInCanon, Outpost 32]
-
A.
inCanonWith
Indicates that two or more works, events, or elements are officially recognized as belonging to the same narrative continuity or canon.
-
B.
canonizedAs
Indicates that an authority, typically a religious institution, has formally declared someone to be a saint or holy figure.
-
C.
designationCategory
chosen
Indicates the classification or type of designation assigned to an entity within a broader designation system.
-
D.
inCanonAuthor
Indicates that an author is officially recognized as part of the established canon within a particular fictional or literary universe.
-
E.
canonicallyReferredToAs
Indicates that one entity is the officially recognized or standard name or label by which another entity is known.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 29, 2026, 9:03 p.m.