Triple
T32486610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tayo creole |
E830260
|
entity |
| Predicate | developedFromContactBetween |
P1245
|
FINISHED |
| Object | French colonists |
—
|
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: French colonists | Statement: [Tayo creole, developedFromContactBetween, French colonists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedFromContactBetween Context triple: [Tayo creole, developedFromContactBetween, French colonists]
-
A.
isInContactWith
Indicates that two entities are physically touching or directly connected so that contact between them is established.
-
B.
developedFrom
chosen
Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
-
C.
historicalContactWith
Indicates that two entities have interacted or been in communication with each other at some point in the past.
-
D.
developedInCase
Indicates that something (such as a method, argument, or principle) was formulated, articulated, or established within the context of a particular case.
-
E.
hasContactInfluenceFrom
Indicates that one entity’s state, behavior, or properties are directly affected or altered through physical or direct contact with another entity.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 12:58 a.m.