Triple
T21294856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 12 Dress (British Army) |
E524893
|
entity |
| Predicate | appliesInBranch |
P51210
|
FINISHED |
| Object | regular army |
—
|
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: regular army | Statement: [No. 12 Dress (British Army), appliesInBranch, regular army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesInBranch Context triple: [No. 12 Dress (British Army), appliesInBranch, regular army]
-
A.
presentInBranch
chosen
Indicates that something exists or is available within a specific branch or subdivision of a larger organization or structure.
-
B.
isOnBranch
Indicates that one entity is physically positioned atop or supported by a branch of another entity.
-
C.
appliesFrom
Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
-
D.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
E.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73857784881908c3b8418a4c00c1e |
completed | April 21, 2026, 8:41 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:04 p.m.