Triple
T35016029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nightosphere |
E1010054
|
entity |
| Predicate | hasPortalIn |
P44087
|
FINISHED |
| Object | Tree Fort |
—
|
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: Tree Fort | Statement: [Nightosphere, hasPortalIn, Tree Fort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortalIn Context triple: [Nightosphere, hasPortalIn, Tree Fort]
-
A.
hasPortal
chosen
Indicates that one entity possesses or provides access to a portal connecting to another location or entity.
-
B.
hasPortico
Indicates that one entity (typically a building or structure) features a portico as part of its architectural design.
-
C.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
-
D.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
E.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: May 3, 2026, 4:01 p.m.