Triple
T837371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life Guards |
E18097
|
entity |
| Predicate | peacetimeDuties |
P7158
|
FINISHED |
| Object | public duties in London |
—
|
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: public duties in London | Statement: [Life Guards, peacetimeDuties, public duties in London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peacetimeDuties Context triple: [Life Guards, peacetimeDuties, public duties in London]
-
A.
peacetimeRole
chosen
Indicates the role, function, or duties an entity holds during periods of peace rather than during wartime or conflict.
-
B.
peacetimeParent
Indicates that one entity is recognized as the parent of another during periods of peace, as opposed to wartime or conflict conditions.
-
C.
hasPeacekeepingRole
Indicates that an entity holds a responsibility or function related to maintaining or enforcing peace, often in a conflict or post-conflict context.
-
D.
maintainedPeaceWith
Indicates that two entities sustained a state of peace or non-conflict with each other over a period of time.
-
E.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abcf69888190b342363978273ae2 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7dfc5c8190890c9df485d73a86 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.