Triple
T10705112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bènizàa |
E252382
|
entity |
| Predicate | hasIdentityFeature |
P40349
|
FINISHED |
| Object | Distinct name from exonym "Zapotec" |
—
|
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: Distinct name from exonym "Zapotec" | Statement: [Bènizàa, hasIdentityFeature, Distinct name from exonym "Zapotec"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIdentityFeature Context triple: [Bènizàa, hasIdentityFeature, Distinct name from exonym "Zapotec"]
-
A.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
B.
hasIdentityComponent
chosen
Indicates that an entity includes or is associated with a specific component that contributes to or defines its identity.
-
C.
supportsIdentity
Indicates that one entity upholds, validates, or reinforces the identity, self-concept, or role of another entity.
-
D.
hasFeatureID
Indicates that an entity is associated with a specific feature identified by a unique ID.
-
E.
hasSocialIdentity
Indicates that an entity possesses or is associated with a particular social identity, such as a role, group membership, or socially recognized status.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fddeb060819094cd125a68070eb2 |
completed | April 9, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8ea6408190a800f9cb57372189 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:12 p.m.