Triple
T24815018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammam ibn Munabbih |
E620894
|
entity |
| Predicate | followedGeneration |
P156149
|
FINISHED |
| Object | generation after the Companions |
—
|
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: generation after the Companions | Statement: [Hammam ibn Munabbih, followedGeneration, generation after the Companions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedGeneration Context triple: [Hammam ibn Munabbih, followedGeneration, generation after the Companions]
-
A.
followsGenerationsOf
Indicates that one entity comes after and is separated from another by multiple generations in a lineage or succession.
-
B.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
-
C.
laterGenerationOf
chosen
Indicates that one entity belongs to a generation that comes chronologically after the generation of another entity.
-
D.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
E.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:02 a.m.