Triple
T4360796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bin Abdullah |
E98654
|
entity |
| Predicate | followsElementType |
P55769
|
FINISHED |
| Object | personal given name |
—
|
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: personal given name | Statement: [bin Abdullah, followsElementType, personal given name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsElementType Context triple: [bin Abdullah, followsElementType, personal given name]
-
A.
followsFrom
Indicates that one fact, event, or state logically or causally results from, is implied by, or comes as a consequence of another.
-
B.
followsCharacterType
Indicates that one character’s behavior, role, or traits are patterned after, derived from, or constrained by a specified character type.
-
C.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
D.
followsComponent
Indicates that one component comes after or succeeds another component in a defined sequence or structure.
-
E.
followedByComponent
Indicates that one component directly succeeds another component in a defined sequence or order.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e3220881909dc9d02ab024abf5 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:16 p.m.