Triple
T37456727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hive (StarCraft Zerg structure) |
E930817
|
entity |
| Predicate | enablesAirTech |
P188330
|
FINISHED |
| Object | Greater Spire tech |
—
|
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: Greater Spire tech | Statement: [Hive (StarCraft Zerg structure), enablesAirTech, Greater Spire tech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesAirTech Context triple: [Hive (StarCraft Zerg structure), enablesAirTech, Greater Spire tech]
-
A.
airCapability
Indicates that an entity possesses the ability or resources to operate or project power in the air (e.g., through aircraft, air defenses, or related systems).
-
B.
airService
Indicates that an air transportation service (such as flights or air routes) is provided or operates between the related entities.
-
C.
usableInAir
Indicates that an entity can function or be operated effectively while in the air.
-
D.
airServiceType
Indicates the specific category or nature of an air transportation service provided or used in the relationship.
-
E.
hasAirComponent
Indicates that something includes, contains, or is associated with an air-related component or element.
- F. None of above. chosen
Provenance (4 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_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.