Triple
T34464042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titular Archbishop of Samosata |
E884721
|
entity |
| Predicate | isResidentialSee |
P179399
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Titular Archbishop of Samosata, isResidentialSee, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResidentialSee Context triple: [Titular Archbishop of Samosata, isResidentialSee, false]
-
A.
isResidential
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
B.
isResidentialOptionFor
Indicates that something serves as a housing or living arrangement available to a particular person or group.
-
C.
isResidentialUnitOf
Indicates that a specific residential unit (e.g., apartment, house) belongs to or is part of a larger property, building, or complex.
-
D.
isResidentialBuildingIn
Indicates that a residential building is located within or belongs to a specified geographic area or administrative region.
-
E.
hasResidentialBuilding
Indicates that an entity possesses, contains, or is associated with a residential building as part of its properties or components.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71fb0172c81908f23e95ff16b0dec |
completed | May 3, 2026, 10:13 a.m. |
Created at: May 1, 2026, 2 a.m.