Triple
T6620344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7th Dragoon Guards |
E149656
|
entity |
| Predicate | laterEvolution |
P13185
|
FINISHED |
| Object | converted to armoured role |
—
|
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: converted to armoured role | Statement: [7th Dragoon Guards, laterEvolution, converted to armoured role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterEvolution Context triple: [7th Dragoon Guards, laterEvolution, converted to armoured role]
-
A.
futureEvolution
Indicates a predicted or potential future development or transformation of one entity into another.
-
B.
laterSpecies
Indicates that one species appears or evolves later in time relative to another species.
-
C.
laterDevelopments
chosen
Indicates that subsequent events, changes, or outcomes occurred following an earlier situation or state.
-
D.
evolves
Indicates that one entity undergoes a process of gradual change or development into another, typically more advanced or different, state or form.
-
E.
evolutionaryPhase
Indicates the stage or period an entity is in within a broader process of gradual development or evolution.
- 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_69c687ed8a9c81908bb671717cb192ef |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:58 p.m.