Triple
T22247757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukedom of Atholl |
E549888
|
entity |
| Predicate | privateArmyStatus |
P147539
|
FINISHED |
| Object | ceremonial infantry regiment |
—
|
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: ceremonial infantry regiment | Statement: [Dukedom of Atholl, privateArmyStatus, ceremonial infantry regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privateArmyStatus Context triple: [Dukedom of Atholl, privateArmyStatus, ceremonial infantry regiment]
-
A.
legalStatusOfArmy
Indicates the legal status or standing of an army under applicable laws or regulations.
-
B.
militaryBaseStatus
Indicates the operational condition or readiness state of a military base at a given time.
-
C.
militaryStatus
Indicates the relationship between an entity and a military organization in terms of service condition, such as active duty, reserve, veteran, or non-military status.
-
D.
armamentStatus
Indicates the current condition or readiness level of an entity’s weapons or military equipment.
-
E.
regimentalStatus
Indicates the formal organizational state or condition of a military regiment within a given structure or timeframe.
- F. None of above. chosen
Provenance (4 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f13219dc3481908dd987c4e98623e6 |
completed | April 28, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:38 p.m.