Triple
T37170412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | church in Philemon’s house |
E920892
|
entity |
| Predicate | likelyLocation |
P114235
|
FINISHED |
| Object | Colossae |
—
|
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: Colossae | Statement: [church in Philemon’s house, likelyLocation, Colossae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyLocation Context triple: [church in Philemon’s house, likelyLocation, Colossae]
-
A.
likelyLocatedIn
chosen
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
B.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
C.
likelyRegion
Indicates that an entity is probably located in, associated with, or originates from a particular geographic region.
-
D.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
-
E.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.