Triple
T32389688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Белая Троицкая церковь |
E827634
|
entity |
| Predicate | имеет статус |
P133403
|
FINISHED |
| Object | действующий храм (предположительно) |
—
|
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: действующий храм (предположительно) | Statement: [Белая Троицкая церковь, имеет статус, действующий храм (предположительно)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеет статус Context triple: [Белая Троицкая церковь, имеет статус, действующий храм (предположительно)]
-
A.
isStatusOf
chosen
Indicates that a particular status or condition is assigned to, or characterizes, a specific entity.
-
B.
hadOfficialStatus
Indicates that an entity possessed a formally recognized or legally sanctioned status within an official system or authority.
-
C.
hasStatusLabel
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
D.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
E.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 12:52 a.m.