Triple
T2688388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic Evangelical Church |
E57538
|
entity |
| Predicate | hasMainWorkArea |
P14400
|
FINISHED |
| Object | Social work |
—
|
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: Social work | Statement: [Coptic Evangelical Church, hasMainWorkArea, Social work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainWorkArea Context triple: [Coptic Evangelical Church, hasMainWorkArea, Social work]
-
A.
hasCoreArea
chosen
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
-
B.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
C.
hasWorkingMode
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
D.
hasWaitingArea
Indicates that an entity provides or includes a designated space where people can wait before receiving a service or proceeding to another area.
-
E.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9f1ba3081909a349a2f30f8f9c9 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.