Triple
T3833807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of the Universe |
E91078
|
entity |
| Predicate | temporaryStructure |
P50685
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Court of the Universe, temporaryStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporaryStructure Context triple: [Court of the Universe, temporaryStructure, true]
-
A.
temporaryClosure
Indicates that an entity is closed or unavailable for a limited, non-permanent period of time.
-
B.
temporaryHomeOf
Indicates that one entity serves as a non-permanent or interim place of residence or storage for another entity.
-
C.
isTemporary
chosen
Indicates that the relationship, state, or condition holds only for a limited or non-permanent duration.
-
D.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
E.
currentStructure
Indicates that an entity is the present or active structural configuration or organization associated with another entity.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb88b8a8819082d4bdbc5bc45366 |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.