Triple
T5804126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Barracks, Windsor |
E128698
|
entity |
| Predicate | hasMess |
P13854
|
FINISHED |
| Object | officers’ mess |
—
|
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: officers’ mess | Statement: [Victoria Barracks, Windsor, hasMess, officers’ mess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMess Context triple: [Victoria Barracks, Windsor, hasMess, officers’ mess]
-
A.
hasMessenger
Indicates that one entity uses or is associated with another entity as a messenger or intermediary for communication.
-
B.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
C.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
D.
has
chosen
Indicates that one entity possesses, owns, contains, or includes another entity as part of its state or composition.
-
E.
hasSept
Indicates that one entity possesses, contains, or is associated with a sept (a subdivision or clan group) in relation to another entity.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1304588190b59a18fb7b70a60f |
completed | March 22, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.