Triple
T23203658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gen. of the Armies |
E580384
|
entity |
| Predicate | washingtonEffectiveDateBackdatedTo |
P66767
|
FINISHED |
| Object | July 4, 1776 |
—
|
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: July 4, 1776 | Statement: [Gen. of the Armies, washingtonEffectiveDateBackdatedTo, July 4, 1776]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: washingtonEffectiveDateBackdatedTo Context triple: [Gen. of the Armies, washingtonEffectiveDateBackdatedTo, July 4, 1776]
-
A.
lessEffectiveAt
Indicates that one entity has a reduced ability or lower level of success in performing, influencing, or achieving a particular action or outcome compared to another.
-
B.
decisionEffectiveDate
chosen
Indicates the date on which a particular decision becomes valid, operative, or officially takes effect.
-
C.
repealEffectiveIn
Indicates that a repeal of a law, rule, or regulation becomes legally operative within a specified jurisdiction or context.
-
D.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
E.
appliedDate
Indicates the date on which an application or request was submitted or made.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907b3e88819088a397a99456bf77 |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.