Triple
T30115036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spooner Act |
E765391
|
entity |
| Predicate | specifiedAlternativeRoute |
P19868
|
FINISHED |
| Object | Nicaragua |
—
|
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: Nicaragua | Statement: [Spooner Act, specifiedAlternativeRoute, Nicaragua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiedAlternativeRoute Context triple: [Spooner Act, specifiedAlternativeRoute, Nicaragua]
-
A.
alternativeRoute
chosen
Indicates that there exists a different path or option that can be taken instead of the primary or original route.
-
B.
trailAlternativeName
Indicates that an entity (such as a trail) is known by an alternative or secondary name.
-
C.
alternativeTerminus
Indicates that something serves as another possible endpoint or final destination in place of, or in addition to, a primary terminus.
-
D.
alternativeOutcomeTo
Indicates that one outcome serves as a different possible result or scenario in place of another outcome.
-
E.
alternativeImplementation
Indicates that one implementation serves as a substitute or different way of realizing the same functionality or specification as another implementation.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 7:11 p.m.