Triple
T29189437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars: Galactic Battlegrounds |
E739951
|
entity |
| Predicate | featuresStructureType |
P81514
|
FINISHED |
| Object | command center |
—
|
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: command center | Statement: [Star Wars: Galactic Battlegrounds, featuresStructureType, command center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresStructureType Context triple: [Star Wars: Galactic Battlegrounds, featuresStructureType, command center]
-
A.
featuresStructure
chosen
Indicates that one entity possesses, exhibits, or incorporates a particular structure as a notable characteristic or component.
-
B.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
C.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
D.
superstructureType
Indicates the specific kind or design category of a structure’s superstructure that an entity possesses or is associated with.
-
E.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: April 28, 2026, 12:01 p.m.