Triple
T1028748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Cross |
E22199
|
entity |
| Predicate | retroactiveTo |
P1639
|
FINISHED |
| Object | 1854-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: 1854-01-01 | Statement: [Victoria Cross, retroactiveTo, 1854-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retroactiveTo Context triple: [Victoria Cross, retroactiveTo, 1854-01-01]
-
A.
retrocededTo
Indicates that control, ownership, or rights over something were returned or transferred back from one entity to another.
-
B.
doesNotApplyRetroactivelyTo
chosen
Indicates that a rule, law, or condition does not affect events, actions, or situations that occurred before it came into effect.
-
C.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
D.
enactedAfter
Indicates that one enactment event occurred later in time than another enactment event.
-
E.
reaffirmedOn
Indicates that a prior decision, statement, or agreement was confirmed or validated again on a specific date or occasion.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95d35888190a20593a278175df7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7276180819085c6b23501a6a6e0 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.