Triple
T33687741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tangere |
E863086
|
entity |
| Predicate | famousUsageSpeaker |
P84993
|
FINISHED |
| Object | Jesus |
—
|
NE NERFINISHED |
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: Jesus | Statement: [Tangere, famousUsageSpeaker, Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousUsageSpeaker Context triple: [Tangere, famousUsageSpeaker, Jesus]
-
A.
notableSpeechBy
Indicates that a particular speech or address is notably given or delivered by a specific entity.
-
B.
famousLineSpeaker
chosen
Indicates that the subject is the person who spoke or delivered the famous line referenced by the object.
-
C.
famousIndividual
Indicates that an individual is widely known and recognized by a large number of people, typically for notable achievements, status, or public visibility.
-
D.
usedBySpeakers
Indicates that something (such as a resource, tool, or method) is employed or utilized by speakers.
-
E.
notableSpeechAssociated
Indicates that a notable or significant speech is associated with a particular entity, such as a person, event, or location.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:43 a.m.