Triple
T27244467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bey of Constantine |
E687299
|
entity |
| Predicate | hasEarlierHolder |
P17684
|
FINISHED |
| Object | Salah Bey |
—
|
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: Salah Bey | Statement: [Bey of Constantine, hasEarlierHolder, Salah Bey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlierHolder Context triple: [Bey of Constantine, hasEarlierHolder, Salah Bey]
-
A.
hasPreviousHolder
chosen
Indicates that an entity was formerly held, occupied, or possessed by another specified entity before the current one.
-
B.
hasFirstHolder
Indicates that an entity is associated with the earliest or original holder (e.g., owner, position-bearer, or title-holder) of something.
-
C.
hasCurrentHolder
Indicates that a specified entity is the present holder, possessor, or occupant of another entity (such as a position, title, asset, or object).
-
D.
hasOlderSelfIn
Indicates that an entity is related to another entity that represents its older version or state within a given context.
-
E.
hasEarlierPhase
Indicates that one phase occurs before another phase in a process or sequence.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 10:40 a.m.