Triple
T28840037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snatchers |
E728288
|
entity |
| Predicate | legalStatusUnderMinistry |
P84060
|
FINISHED |
| Object | semi-officially sanctioned |
—
|
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: semi-officially sanctioned | Statement: [Snatchers, legalStatusUnderMinistry, semi-officially sanctioned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusUnderMinistry Context triple: [Snatchers, legalStatusUnderMinistry, semi-officially sanctioned]
-
A.
methodOfMinistry
Indicates the specific way or approach through which ministry or religious service is carried out.
-
B.
typeOfMinistry
Indicates the specific category or kind of ministry that an entity belongs to or represents.
-
C.
legalStatusOfAuthority
chosen
Indicates the legal status or standing that a particular authority holds within a given legal or regulatory framework.
-
D.
hasGovernmentalStatus
Indicates that an entity holds an official governmental role, recognition, or classification within a political or administrative system.
-
E.
governingStatus
Indicates the political or administrative condition under which an entity is currently governed or exercising governing authority.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 28, 2026, 6:40 a.m.