Triple
T24416450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agua Negra Tunnel |
E615595
|
entity |
| Predicate | isInternationalProject |
P1499
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Agua Negra Tunnel, isInternationalProject, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInternationalProject Context triple: [Agua Negra Tunnel, isInternationalProject, true]
-
A.
isInternational
chosen
Indicates that something has a connection to, involves, or extends across more than one country.
-
B.
isInternationalStandard
Indicates that something has been formally recognized or adopted as a standard at the international level.
-
C.
hasInternationalVersion
Indicates that an entity has a corresponding version or counterpart adapted for use in multiple countries or international contexts.
-
D.
hasInternationalStatus
Indicates that an entity holds a recognized status, role, or standing at the international level rather than being limited to a single country or local jurisdiction.
-
E.
internationalTeam
Indicates that a team is composed of members from multiple countries or operates across national boundaries.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2958645248190a22bd0b8bcc2dfe2 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:13 a.m.