Triple
T33447839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Messenger |
E856554
|
entity |
| Predicate | perceivedStatusByFollowers |
P177619
|
FINISHED |
| Object | divinely appointed messenger |
—
|
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: divinely appointed messenger | Statement: [The Messenger, perceivedStatusByFollowers, divinely appointed messenger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceivedStatusByFollowers Context triple: [The Messenger, perceivedStatusByFollowers, divinely appointed messenger]
-
A.
estimatedFollowers
Indicates that a numerical value represents an approximation of how many followers an entity has.
-
B.
goalForFollowers
Indicates that an entity sets or represents a goal or target specifically intended for its followers.
-
C.
followsApproximately
Indicates that one entity follows another in sequence or order, but with some allowable deviation or inexactness in timing, position, or pattern.
-
D.
hasFollowers
Indicates that an entity is followed or subscribed to by one or more other entities.
-
E.
someFollowersBecame
Indicates that a subset of an entity’s followers transitioned into a new role, state, or category associated with that entity.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:37 a.m.