Triple
T37456663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatchery |
E930816
|
entity |
| Predicate | startingStructureFor |
P100797
|
FINISHED |
| Object | Zerg player |
—
|
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: Zerg player | Statement: [Hatchery, startingStructureFor, Zerg player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingStructureFor Context triple: [Hatchery, startingStructureFor, Zerg player]
-
A.
spawnStructure
chosen
Indicates that an entity causes a new structure to be created or instantiated in the environment.
-
B.
builtStructureFor
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
-
C.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
D.
producesStructure
Indicates that one entity generates, forms, or creates a physical or conceptual structure as a result of its action or function.
-
E.
plannedStructure
Indicates that one entity is a structure that is intended or designed to be built or established in the future, rather than already existing.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00cbae75988190974f5b45a2e62326 |
completed | May 10, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_6a00cabe4c5881909cca5efbe494e0d1 |
completed | May 10, 2026, 6:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.