Triple
T30115038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spooner Act |
E765391
|
entity |
| Predicate | appropriatedFundsFor |
P184305
|
FINISHED |
| Object | construction of an isthmian canal |
—
|
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: construction of an isthmian canal | Statement: [Spooner Act, appropriatedFundsFor, construction of an isthmian canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appropriatedFundsFor Context triple: [Spooner Act, appropriatedFundsFor, construction of an isthmian canal]
-
A.
mainUseOfFunds
Indicates how the primary portion of allocated or received funds is intended to be used or applied.
-
B.
budgetFundsFor
chosen
Indicates allocating or designating financial resources for a specific purpose, project, or entity.
-
C.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
D.
authorizedAppropriations
Indicates that a governing body has formally approved the allocation of funds for a specific purpose or activity.
-
E.
excludedUseOfFundsFor
Indicates that certain funds are prohibited from being used for a specified purpose or activity.
- 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_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 29, 2026, 7:11 p.m.