Triple
T23617435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empire universe |
E583211
|
entity |
| Predicate | includesSettingType |
P101663
|
FINISHED |
| Object | corporate offices |
—
|
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: corporate offices | Statement: [Empire universe, includesSettingType, corporate offices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSettingType Context triple: [Empire universe, includesSettingType, corporate offices]
-
A.
hasSetting
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
B.
hasSettingDetail
Indicates that an entity is associated with a specific contextual or environmental detail that characterizes its setting.
-
C.
includesFeatureTypes
chosen
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
-
D.
hasSettingRole
Indicates that an entity participates in a setting by fulfilling a specific contextual or functional role within it.
-
E.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
- 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_69e248fbcd9081908ba08913f9d30826 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b175b2208190a78e1d4aac191709 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:45 p.m.