Triple
T25793148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cangin languages |
E649602
|
entity |
| Predicate | areHistoricallyRelatedTo |
P16345
|
FINISHED |
| Object | Serer language |
—
|
NE NERFINISHED |
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: Serer language | Statement: [Cangin languages, areHistoricallyRelatedTo, Serer language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areHistoricallyRelatedTo Context triple: [Cangin languages, areHistoricallyRelatedTo, Serer language]
-
A.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
B.
historicallyLinked
chosen
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
C.
historicallyGroupedWith
Indicates that two or more entities have been associated or classified together in the past based on historical context, usage, or tradition, even if they are no longer grouped that way.
-
D.
historicalRelationsWith
Indicates a relationship where one entity has documented or recognized connections, interactions, or associations with another entity in the past.
-
E.
hasGenealogicalRelation
Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ff0074908190a36e4b960dd43734 |
completed | May 2, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 6:01 a.m.