Triple
T34380851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinmal |
E882432
|
entity |
| Predicate | foundedAsBaseBy |
P198048
|
FINISHED |
| Object | Ibn Tumart |
—
|
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: Ibn Tumart | Statement: [Tinmal, foundedAsBaseBy, Ibn Tumart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsBaseBy Context triple: [Tinmal, foundedAsBaseBy, Ibn Tumart]
-
A.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
B.
foundedAsCityBy
Indicates that a city was originally established or created by a specific person, group, or authority.
-
C.
foundedFrom
Indicates that an entity was established or originated starting from a particular source, place, or prior entity.
-
D.
possiblyFoundedBy
Indicates that an entity may have been founded or established by another entity, but this founding relationship is uncertain or not definitively confirmed.
-
E.
foundedAsSettlementFor
Indicates that one entity was originally established specifically to serve as a settlement for another entity (such as a group, population, or community).
- F. None of above. chosen
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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
| PDg | Predicate description generation | batch_69fec4cee6a081908139ea6aa608f729 |
completed | May 9, 2026, 5:23 a.m. |
Created at: May 1, 2026, 1:59 a.m.