Triple
T3982583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khoe-Kwadi |
E86793
|
entity |
| Predicate | hasMemberStatus |
P18012
|
FINISHED |
| Object | Kwadi is extinct |
—
|
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: Kwadi is extinct | Statement: [Khoe-Kwadi, hasMemberStatus, Kwadi is extinct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberStatus Context triple: [Khoe-Kwadi, hasMemberStatus, Kwadi is extinct]
-
A.
membershipStatus
chosen
Indicates the current state or level of an entity’s participation or affiliation within a group, organization, or program.
-
B.
hasMemberState
Indicates that an entity includes or comprises another entity as one of its constituent member states within a larger organizational or political structure.
-
C.
hasMembershipBy
Indicates that an entity holds or acquires membership in a group, organization, or program by means of a specified agent, process, or instrument.
-
D.
hasAssociateMember
Indicates that an entity has another entity connected to it in a non-full, typically limited or secondary, membership capacity.
-
E.
membershipAsOf
Indicates that one entity is a member of another entity or group at a specific point in time or as of a given date.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa3ef7ac8190abe02f440ff83c43 |
completed | March 9, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69aef8f492ac819089dbb9436dbcdd2b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.