Triple
T35446449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeropuerto Internacional de Carrasco |
E1024498
|
entity |
| Predicate | terminalDesignFeature |
P95346
|
FINISHED |
| Object | curved roof |
—
|
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: curved roof | Statement: [Aeropuerto Internacional de Carrasco, terminalDesignFeature, curved roof]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalDesignFeature Context triple: [Aeropuerto Internacional de Carrasco, terminalDesignFeature, curved roof]
-
A.
terminalDesign
Indicates a relationship where an entity is responsible for or characterized by the design or configuration of a terminal or terminal-like interface.
-
B.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
C.
insigniaDesignFeature
Indicates a design element or characteristic that forms part of an insignia.
-
D.
typicalDesignElement
chosen
Indicates that something is a common or characteristic design feature typically found in or associated with another entity.
-
E.
testedDesignFeature
Indicates that a specific design feature has been subjected to a test or evaluation process.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:04 p.m.