Triple
T29952420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vale do Paraíba region |
E760803
|
entity |
| Predicate | hasAerospaceHub |
P168289
|
FINISHED |
| Object | São José dos Campos |
—
|
NE NERFINISHED |
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: São José dos Campos | Statement: [Vale do Paraíba region, hasAerospaceHub, São José dos Campos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAerospaceHub Context triple: [Vale do Paraíba region, hasAerospaceHub, São José dos Campos]
-
A.
isCivilAviationHub
Indicates that a location serves as a central node for civil (non-military) air transport operations, such as passenger and cargo flights.
-
B.
hasSpaceport
Indicates that a location or entity possesses or hosts a spaceport facility for spacecraft operations.
-
C.
hasMajorAirport
Indicates that a location possesses at least one significant airport that serves as a primary hub for air travel in that area.
-
D.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional airport.
-
E.
hasAirportAccessTo
Indicates that one location or entity has direct access to another via an airport connection or service.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67837aa6c8190a74eea05d3a6c4b1 |
completed | May 2, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:26 p.m.