Triple
T28460104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Federalist No. 29 |
E720126
|
entity |
| Predicate | statesPurposeOfMilitia |
P185632
|
FINISHED |
| Object | national security |
—
|
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: national security | Statement: [The Federalist No. 29, statesPurposeOfMilitia, national security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statesPurposeOfMilitia Context triple: [The Federalist No. 29, statesPurposeOfMilitia, national security]
-
A.
hadMilitia
Indicates that an entity maintained or was associated with a militia force during a certain period.
-
B.
purposeOfConfederation
Indicates that one entity exists, is formed, or is used for the specific purpose or objective of a particular confederation.
-
C.
typeOfMilitia
Indicates the specific kind or category of militia to which an entity belongs or is classified.
-
D.
objectiveOfUSForces
Indicates that a specified goal, target, or mission serves as an objective assigned to or pursued by U.S. military forces.
-
E.
goalOfDuties
Indicates that something is the intended objective or purpose that a set of duties or responsibilities is meant to achieve.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: April 28, 2026, 2:38 a.m.