Triple
T37664128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illager |
E937782
|
entity |
| Predicate | canBeLeader |
P48120
|
FINISHED |
| Object | Raid captain |
—
|
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: Raid captain | Statement: [Illager, canBeLeader, Raid captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeLeader Context triple: [Illager, canBeLeader, Raid captain]
-
A.
canBeLedBy
Indicates that one entity is capable of being guided, directed, or managed by another entity.
-
B.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
C.
requiresLeaderQualification
Indicates that an entity can only assume or perform a leadership role if a specified qualification or credential is met.
-
D.
establishedUnderLeader
Indicates that an entity was founded, created, or formally established during the tenure or authority of a specific leader.
-
E.
canBeChairOf
chosen
Indicates that an entity has the eligibility or capacity to serve as the chair (leader) of a specified group, committee, or organization.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: May 3, 2026, 4:18 p.m.