Triple
T11974628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Clause |
E285006
|
entity |
| Predicate | historicalConcern |
P48635
|
FINISHED |
| Object | fear of large standing armies |
—
|
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: fear of large standing armies | Statement: [Army Clause, historicalConcern, fear of large standing armies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalConcern Context triple: [Army Clause, historicalConcern, fear of large standing armies]
-
A.
historicalIssue
Indicates that one entity is a past or previously existing edition, version, or instance of another entity, typically within a chronological sequence.
-
B.
historicalFocus
Indicates that something is primarily concerned with, centered on, or devoted to a particular historical period, event, or theme.
-
C.
historicalReason
Indicates that one entity exists, occurs, or is justified because of causes, events, or circumstances rooted in the past of another entity.
-
D.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
E.
historicalInterest
chosen
Indicates that one entity has a notable relevance, appeal, or significance to the study or understanding of the past.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9039107e48190ae4c4efd6257dd3c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.