Triple
T27727951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | stoning of Paul |
E697352
|
entity |
| Predicate | tookPlaceInProvince |
P100087
|
FINISHED |
| Object | Roman province of Galatia |
—
|
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: Roman province of Galatia | Statement: [stoning of Paul, tookPlaceInProvince, Roman province of Galatia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPlaceInProvince Context triple: [stoning of Paul, tookPlaceInProvince, Roman province of Galatia]
-
A.
heldInProvince
chosen
Indicates that an event or activity takes place within the boundaries of a specified province.
-
B.
tookPlaceInAdministrativeEntity
Indicates that an event or occurrence happened within the jurisdiction or boundaries of a specific administrative entity.
-
C.
stationedInProvince
Indicates that an entity is assigned or based in a particular province as its location or area of operation.
-
D.
takesPlaceInRegion
Indicates that an event or occurrence happens within the boundaries of a specified geographic or administrative region.
-
E.
tookPlaceInState
Indicates that an event or occurrence happened within the geographical or political boundaries of a specific state.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f636417d448190bf3f54faeadabadc |
completed | May 2, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:10 p.m.