Triple
T26988141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Ezekiel |
E679787
|
entity |
| Predicate | communityRuled |
P98193
|
FINISHED |
| Object | the Kingdom |
—
|
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: the Kingdom | Statement: [King Ezekiel, communityRuled, the Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communityRuled Context triple: [King Ezekiel, communityRuled, the Kingdom]
-
A.
communityAspect
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
B.
communalPolicy
chosen
Indicates a policy or rule that is collectively established, shared, or applied within a community or group.
-
C.
community
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
D.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
E.
communityBased
Indicates that something is organized, developed, or delivered within and by a local community, emphasizing local participation, control, and context.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 6:50 a.m.