Triple
T4767923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zechariah |
E105856
|
entity |
| Predicate | doubted |
P59223
|
FINISHED |
| Object | Gabriel’s message about the birth of a son |
—
|
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: Gabriel’s message about the birth of a son | Statement: [Zechariah, doubted, Gabriel’s message about the birth of a son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doubted Context triple: [Zechariah, doubted, Gabriel’s message about the birth of a son]
-
A.
disputed
Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
-
B.
determined
Indicates that an entity has firmly decided on a course of action or conclusion, typically after consideration or effort.
-
C.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
-
D.
demanded
Indicates that one entity forcefully or insistently requested something from another entity.
-
E.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd686dc7b88190b41e8a362701080d |
completed | March 20, 2026, 3:31 p.m. |
Created at: March 20, 2026, 1:21 p.m.