Triple
T14796881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asakyiri |
E347803
|
entity |
| Predicate | identityFunction |
P36583
|
FINISHED |
| Object | provides clan identity to members |
—
|
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: provides clan identity to members | Statement: [Asakyiri, identityFunction, provides clan identity to members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identityFunction Context triple: [Asakyiri, identityFunction, provides clan identity to members]
-
A.
identityBasis
chosen
Indicates that one entity serves as the defining basis, criterion, or foundation for determining the identity of another entity.
-
B.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
C.
convolutionIdentity
Indicates that one element acts as the identity under convolution, leaving the other element unchanged when convolved with it.
-
D.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
E.
typeOfIdentity
Indicates the specific category or nature of identity that characterizes or defines an entity within a given 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd5fdd548190a2ee5e668c2b20b4 |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.