Triple
T35443059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naso Tjër Di language |
E1024404
|
entity |
| Predicate | associatedPeopleExonym |
P77482
|
FINISHED |
| Object | Teribe |
E1704077
|
NE 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: Teribe | Statement: [Naso Tjër Di language, associatedPeopleExonym, Teribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPeopleExonym Context triple: [Naso Tjër Di language, associatedPeopleExonym, Teribe]
-
A.
peopleAssociatedWith
chosen
Indicates that there exists some form of connection, involvement, or relationship between the referenced people.
-
B.
associatedPersonField
Indicates that there is a person linked or connected to the subject in a relevant or contextual way.
-
C.
relatedIdentity
Indicates that two identities are connected or associated with each other in some meaningful way, such as being alternate, linked, or otherwise contextually related.
-
D.
associatedPeopleStatus
Indicates the role, condition, or standing of people who are connected or linked to a given entity or event.
-
E.
associatedBeings
Indicates that two or more beings are linked or connected to each other in some relevant way.
- F. None of above.
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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384a23d9c881908280b3e002ad881b |
completed | June 21, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.