Triple
T25741968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Cross |
E648242
|
entity |
| Predicate | eligibilityReformedOn |
P5212
|
FINISHED |
| Object | 1993-01-01 |
—
|
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: 1993-01-01 | Statement: [Military Cross, eligibilityReformedOn, 1993-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibilityReformedOn Context triple: [Military Cross, eligibilityReformedOn, 1993-01-01]
-
A.
eligibilityPeriod
Indicates the span of time during which an entity qualifies for or is allowed to receive a particular benefit, service, or status.
-
B.
eligibilityPeriodStartYear
Indicates the calendar year in which an entity’s eligibility period begins.
-
C.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
D.
legalStatusAfterReform
Indicates the legal status or condition an entity holds following the implementation of a specific reform or legal change.
-
E.
reformDate
chosen
Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 22, 2026, 3:45 a.m.