Triple
T6458781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | church in Antioch |
E142061
|
entity |
| Predicate | pastEvent |
P22468
|
FINISHED |
| Object | Barnabas sent from Jerusalem to Antioch (Acts 11) |
—
|
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: Barnabas sent from Jerusalem to Antioch (Acts 11) | Statement: [church in Antioch, pastEvent, Barnabas sent from Jerusalem to Antioch (Acts 11)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pastEvent Context triple: [church in Antioch, pastEvent, Barnabas sent from Jerusalem to Antioch (Acts 11)]
-
A.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
B.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
C.
publishedEvent
Indicates that an entity has formally released or made an event publicly available or announced.
-
D.
significantEventEnd
Indicates the point in time when a significant event or occurrence comes to a close or is considered finished.
-
E.
hadEvent
chosen
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069f347f48190a2b22c5b648b17bd |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:48 p.m.