Triple
T27485126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Bete Giyorgis |
E693715
|
entity |
| Predicate | planView |
P162435
|
FINISHED |
| Object | cross-shaped |
—
|
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: cross-shaped | Statement: [Church of Bete Giyorgis, planView, cross-shaped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planView Context triple: [Church of Bete Giyorgis, planView, cross-shaped]
-
A.
plan
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
B.
planNumber
Indicates that an entity is associated with a specific plan identifier or code used to distinguish it from other plans.
-
C.
planOutcome
Indicates the result or consequence that is expected or produced by a given plan.
-
D.
planType
Indicates the specific category or kind of plan associated with an entity, such as its level, structure, or intended use.
-
E.
presentsView
Indicates that one entity displays or renders another entity as a view or visual interface to a user.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e848b008190bd7314c9a0f884a3 |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:02 p.m.