Triple
T26199950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chach of Alor |
E655201
|
entity |
| Predicate | occupationBeforeRule |
P28984
|
FINISHED |
| Object | minister |
—
|
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: minister | Statement: [Chach of Alor, occupationBeforeRule, minister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupationBeforeRule Context triple: [Chach of Alor, occupationBeforeRule, minister]
-
A.
earlierOccupation
chosen
Indicates that one occupation held by an entity occurred before another occupation in that entity’s work history.
-
B.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
C.
namedAfterOccupationOrRole
Indicates that an entity is named after a specific occupation, profession, or social role associated with a person or group.
-
D.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
E.
occupationDuringAlias
Indicates that an entity held a particular occupation specifically during the time period when it was known by a given alias.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 26, 2026, 8:48 p.m.