Triple
T28458474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMV |
E716782
|
entity |
| Predicate | associatedWithInfrastructureType |
P2560
|
FINISHED |
| Object | airport |
—
|
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: airport | Statement: [MMV, associatedWithInfrastructureType, airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithInfrastructureType Context triple: [MMV, associatedWithInfrastructureType, airport]
-
A.
infrastructureAssociatedWith
Indicates a relationship where a piece of infrastructure is functionally or contextually connected to, supports, or is used by another entity.
-
B.
hasInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
C.
isPartOfInfrastructureType
Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
-
D.
relatedInfrastructure
Indicates that one piece of infrastructure is connected, associated, or functionally related to another infrastructure element.
-
E.
ownedInfrastructureClass
Indicates that an entity possesses or controls infrastructure belonging to a specified class or category.
- 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a0164b052608190adc93240dad50a06 |
completed | May 11, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_6a01637fd3ac8190970eb09650d1e659 |
completed | May 11, 2026, 5:05 a.m. |
Created at: April 28, 2026, 1:55 a.m.