Triple
T38634511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rust (Call of Duty: Modern Warfare 2 map) |
E937541
|
entity |
| Predicate | verticality |
P190938
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Rust (Call of Duty: Modern Warfare 2 map), verticality, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verticality Context triple: [Rust (Call of Duty: Modern Warfare 2 map), verticality, high]
-
A.
hasVerticality
chosen
Indicates that one entity possesses or exhibits vertical orientation, alignment, or extent relative to another reference.
-
B.
verticalLocation
Indicates a vertical positional relationship where one entity is located above or below another along the up-down axis.
-
C.
verticalStructure
Indicates a relationship where one entity is a structure that extends predominantly in the vertical direction relative to another reference or context.
-
D.
targetVertical
Indicates that one entity is directed toward, aligned with, or intended for a specific vertical market, domain, or industry segment.
-
E.
verticalExtent
Indicates the total height or vertical span of an entity or region from its lowest to highest point.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.