Triple
T38620324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ul'dah |
E936847
|
entity |
| Predicate | grandCompanyLeader |
P65676
|
FINISHED |
| Object | Raubahn Aldynn |
—
|
NE NERFINISHED |
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: Raubahn Aldynn | Statement: [Ul'dah, grandCompanyLeader, Raubahn Aldynn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandCompanyLeader Context triple: [Ul'dah, grandCompanyLeader, Raubahn Aldynn]
-
A.
grandCompany
Indicates a relationship where a company is recognized as large, prominent, or of major importance within its context.
-
B.
companyHeaded
Indicates that one entity serves as the leader or chief executive in charge of directing and managing the other entity (the company).
-
C.
generalDirector
Indicates that one entity serves as the general director (top executive or chief manager) of another entity, such as an organization or project.
-
D.
officeHolderLeads
Indicates that the office holder has primary leadership or executive authority over the specified entity (such as an organization, body, or jurisdiction).
-
E.
leaderOfGroup
chosen
Indicates that an entity holds a leadership role or primary authority over a particular group.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:32 p.m.