Triple
T33886921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab-Berber civilization |
E868654
|
entity |
| Predicate | notableThinker |
P603
|
FINISHED |
| Object | Ibn Khaldun |
E99689
|
NE 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: Ibn Khaldun | Statement: [Arab-Berber civilization, notableThinker, Ibn Khaldun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableThinker Context triple: [Arab-Berber civilization, notableThinker, Ibn Khaldun]
-
A.
notableTheorist
Indicates that the subject is recognized as a significant or influential theorist in relation to the object or specified field.
-
B.
notablePhilosopher
chosen
Indicates that the subject is recognized as a philosopher of particular significance or influence.
-
C.
notableMaker
Indicates that one entity is a well-known or significant creator, producer, or manufacturer of the other entity.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableProfessor
Indicates that a person holds or has held a professorship that is distinguished, prominent, or otherwise recognized as notable.
- F. None of above.
Provenance (4 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3676321d0081908d6e4275aa79e457 |
completed | June 20, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:48 a.m.