Triple
T7599558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deputy Lieutenant |
E179947
|
entity |
| Predicate | mayBeDrawnFrom |
P25436
|
FINISHED |
| Object | military background |
—
|
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: military background | Statement: [Deputy Lieutenant, mayBeDrawnFrom, military background]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeDrawnFrom Context triple: [Deputy Lieutenant, mayBeDrawnFrom, military background]
-
A.
mayBeFilledBy
Indicates that one entity has the potential or permission to be occupied, completed, or satisfied by another entity.
-
B.
canBeDepictedAs
Indicates that one entity is capable of being visually represented or illustrated in the form or style of another entity.
-
C.
canBeObtainedFrom
chosen
Indicates that one entity is derivable, producible, or acquirable from another entity as a source or origin.
-
D.
canBeEarnedBy
Indicates that something (such as a reward, status, or resource) is obtainable through the actions, efforts, or qualifications of a particular entity.
-
E.
canBeDesignatedBy
Indicates that one entity is capable of being assigned, labeled, or identified by another entity as its designation.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d7cb288190b40ff5c9a09297d9 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.