Triple
T33949130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Petites Côtes |
E870389
|
entity |
| Predicate | regionAtTimeOfNaming |
P39753
|
FINISHED |
| Object | Upper Louisiana |
—
|
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: Upper Louisiana | Statement: [Les Petites Côtes, regionAtTimeOfNaming, Upper Louisiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionAtTimeOfNaming Context triple: [Les Petites Côtes, regionAtTimeOfNaming, Upper Louisiana]
-
A.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
B.
regionNameCreated
Indicates that a specific region was created with the given name.
-
C.
territoryAtTime
Indicates that a specified territory is associated with or held by an entity during a particular time or time interval.
-
D.
administrativeAreaAtTime
Indicates that an entity was located within or belonged to a specific administrative area during a specified time period.
-
E.
historicalEraOfNaming
chosen
Indicates the historical era or time period during which an entity received its name.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:49 a.m.