Triple
T19924835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derbe |
E478895
|
entity |
| Predicate | roleInActs |
P137850
|
FINISHED |
| Object | site of preaching by Paul and Barnabas |
—
|
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: site of preaching by Paul and Barnabas | Statement: [Derbe, roleInActs, site of preaching by Paul and Barnabas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInActs Context triple: [Derbe, roleInActs, site of preaching by Paul and Barnabas]
-
A.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
roleInRepertoire
Indicates that an entity serves a specific role or function within a larger repertoire, collection, or set of items.
-
D.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
-
E.
actingRoleType
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c88c548190b9b9eccbdd07d977 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.