Triple
T7056288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciboney language |
E164098
|
entity |
| Predicate | likelyContactWith |
P4255
|
FINISHED |
| Object | Taíno language |
—
|
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: Taíno language | Statement: [Ciboney language, likelyContactWith, Taíno language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyContactWith Context triple: [Ciboney language, likelyContactWith, Taíno language]
-
A.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
B.
historicalContactWith
chosen
Indicates that two entities have interacted or been in communication with each other at some point in the past.
-
C.
hasContactInfluenceFrom
Indicates that one entity’s state, behavior, or properties are directly affected or altered through physical or direct contact with another entity.
-
D.
hasKontakion
Indicates that an entity is associated with or possesses a specific kontakion, i.e., a particular liturgical hymn or chant.
-
E.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:38 p.m.