Triple
T555334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospels |
E11929
|
entity |
| Predicate | containsAccountOf |
P16326
|
FINISHED |
| Object | miracles of Jesus |
—
|
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: miracles of Jesus | Statement: [Gospels, containsAccountOf, miracles of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAccountOf Context triple: [Gospels, containsAccountOf, miracles of Jesus]
-
A.
supportsAccountType
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
-
B.
hasAdherent
Indicates that an entity is a follower, supporter, or member attached to another entity (such as a person, organization, belief, or movement).
-
C.
hasAssociateMember
Indicates that an entity has another entity connected to it in a non-full, typically limited or secondary, membership capacity.
-
D.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
E.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991dd7008190a6c1bc8bc832456d |
completed | March 1, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69a494bc1f8c8190904356f3a8e801de |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985952a481908b918350ececf484 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.