Triple
T10533135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 8th Dragoons (France) |
E248493
|
entity |
| Predicate | regimentNumber |
P18684
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [8th Dragoons (France), regimentNumber, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentNumber Context triple: [8th Dragoons (France), regimentNumber, 8]
-
A.
regimentalNumber
chosen
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
-
B.
hasRegimentalIdentity
Indicates that an entity possesses or is associated with a specific regimental identity, such as belonging to or being characterized by a particular regiment.
-
C.
hasBattalionNumber
Indicates that an entity (such as a military unit) is associated with a specific battalion number identifier.
-
D.
regimentalCategory
Indicates the classification or type of regiment to which a military unit or formation belongs.
-
E.
militaryServiceNumber
Indicates the unique identification number assigned to an individual for tracking their record in a military service context.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a19b59c8190b00db7d5813ad37d |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:30 p.m.