Triple
T14153315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Master |
E350742
|
entity |
| Predicate | canBeHeadOf |
P48120
|
FINISHED |
| Object | military order |
—
|
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 order | Statement: [Grand Master, canBeHeadOf, military order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeHeadOf Context triple: [Grand Master, canBeHeadOf, military order]
-
A.
canBeChairOf
chosen
Indicates that an entity has the eligibility or capacity to serve as the chair (leader) of a specified group, committee, or organization.
-
B.
isHeadOf
Indicates that one entity holds the leading or principal authority position over another entity, such as an organization, group, or department.
-
C.
hasHeadOf
Indicates that one entity serves as the leader, chief, or person in charge of another entity (such as an organization, group, or department).
-
D.
mayBeHeadedBy
Indicates that an entity can potentially serve as the leader or head of another entity, but this leadership is not certain or currently established.
-
E.
canBeProclaimedUnder
Indicates that something is eligible or authorized to be formally declared or announced under a specified law, authority, or framework.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6133754881908e1e97db71772deb |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:57 a.m.