Triple
T17269431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicodemus |
E419213
|
entity |
| Predicate | topicOfDialogue |
P126792
|
FINISHED |
| Object | new birth |
—
|
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: new birth | Statement: [Nicodemus, topicOfDialogue, new birth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topicOfDialogue Context triple: [Nicodemus, topicOfDialogue, new birth]
-
A.
topicOfConference
Indicates that a given subject or theme is the main focus or subject matter of a particular conference.
-
B.
primaryTopicOf
Indicates that a given subject is the main or central topic described by another resource (such as a document, page, or record).
-
C.
frequentlyDiscussedIn
Indicates that a topic, subject, or entity is often the focus of conversation, debate, or mention within a particular context or medium.
-
D.
negotiationTopic
Indicates that the associated entities are engaged in a negotiation specifically concerning the referenced topic or subject matter.
-
E.
coveredTopics
Indicates that certain subjects or themes have been addressed or included within a discussion, document, or activity.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4803b48190894b3bb9a4970602 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:40 a.m.