Triple
T23493341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayoreo |
E571634
|
entity |
| Predicate | hasUncontactedGroups |
P152597
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ayoreo, hasUncontactedGroups, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUncontactedGroups Context triple: [Ayoreo, hasUncontactedGroups, true]
-
A.
hasContactState
Indicates that an entity is currently in a specific state or condition regarding its physical or communicative contact with another entity.
-
B.
hasNotableRecipientGroup
Indicates that an entity is associated with a specific group that is recognized as a notable or distinguished recipient of something (e.g., an award, benefit, or honor).
-
C.
hasContactMethod
Indicates that an entity has a specific way or channel through which it can be contacted.
-
D.
hasCommunityGroups
Indicates that an entity is associated with one or more organized community groups or organizations.
-
E.
hasKontakion
Indicates that an entity is associated with or possesses a specific kontakion, i.e., a particular liturgical hymn or chant.
- F. None of above. chosen
Provenance (4 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7de1ab88190b6c2441c63a99713 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:05 p.m.