Triple
T47732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haitian Creole |
E937
|
entity |
| Predicate | historicalPeriodOfFormation |
P1614
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Haitian Creole, historicalPeriodOfFormation, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfFormation Context triple: [Haitian Creole, historicalPeriodOfFormation, 17th century]
-
A.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
B.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
-
C.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
D.
partOfHistoryOf
Indicates that one entity forms a component, episode, or contributing element within the historical development or narrative of another entity.
-
E.
hasHistoricalOrigin
chosen
Indicates that something originated, was first established, or came into existence during a specific historical period or context.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abe7cb481908d969e54032f6c75 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.