Triple
T31594256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mäṣḥafä Fəkkare Iyäsus |
E806179
|
entity |
| Predicate | statusWithinCommunity |
P38813
|
FINISHED |
| Object | central text |
—
|
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: central text | Statement: [Mäṣḥafä Fəkkare Iyäsus, statusWithinCommunity, central text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusWithinCommunity Context triple: [Mäṣḥafä Fəkkare Iyäsus, statusWithinCommunity, central text]
-
A.
statusInCommunity
chosen
Indicates the social standing, role, or level of acceptance an entity holds within a particular community.
-
B.
statusOfCommunity
Indicates the current condition, state, or standing of a community at a given point in time.
-
C.
hasRoleInCommunity
Indicates that an entity holds or performs a specific role, function, or position within a particular community.
-
D.
isCommunityBy
Indicates that something functions as or is recognized as a community defined or established by a particular agent or source.
-
E.
isCommunity
Indicates that an entity functions as or is classified as a community, typically representing a group of individuals connected by shared location, interests, or characteristics.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: April 30, 2026, 10:29 p.m.