Triple
T47704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haitian Creole |
E937
|
entity |
| Predicate | coOfficialWith |
P3084
|
FINISHED |
| Object | French |
—
|
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 | Statement: [Haitian Creole, coOfficialWith, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coOfficialWith Context triple: [Haitian Creole, coOfficialWith, French]
-
A.
isOfficialPortalFor
Indicates that one entity serves as the recognized, authoritative portal or entry point for accessing information or services related to another entity.
-
B.
coRecipientWith
Indicates that two or more entities receive the same item, benefit, or communication together as joint recipients.
-
C.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
D.
officialName
Indicates the formally recognized name assigned to an entity by an authoritative body or source.
-
E.
commissionedBy
Indicates that one entity has been formally requested, authorized, or hired by another entity to create, perform, or carry out something.
- F. None of above. chosen
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_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. |
| PDg | Predicate description generation | batch_69a24c198e74819088a211001d0b54d4 |
completed | Feb. 28, 2026, 1:59 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.