Triple
T24235160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Cochran |
E601853
|
entity |
| Predicate | worksAtInSeries |
P93741
|
FINISHED |
| Object | church choir in rural Kentucky |
—
|
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: church choir in rural Kentucky | Statement: [Arthur Cochran, worksAtInSeries, church choir in rural Kentucky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksAtInSeries Context triple: [Arthur Cochran, worksAtInSeries, church choir in rural Kentucky]
-
A.
worksInSeriesWith
Indicates that one entity collaborates or participates together with another entity within the same series or serialized work.
-
B.
workedOnSeries
Indicates that an entity contributed work to the creation or production of a particular series.
-
C.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
D.
hasWorkInSeriesRole
Indicates that an entity holds a specific role or function within a particular work that is part of a series.
-
E.
workAt
chosen
Indicates that an entity is employed by or performs work for a particular organization, company, or place.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28a9a4b708190851504c302778fd2 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:02 a.m.