Triple
T31897900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bienville Parish, Louisiana |
E814336
|
entity |
| Predicate | hasTimberHistory |
P91454
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bienville Parish, Louisiana, hasTimberHistory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimberHistory Context triple: [Bienville Parish, Louisiana, hasTimberHistory, true]
-
A.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
B.
hasFireHistory
Indicates that an entity has experienced one or more fire events in the past.
-
C.
hasEnvironmentalHistory
chosen
Indicates that an entity is associated with a record or account of its past environmental conditions, impacts, or interactions.
-
D.
hasForestType
Indicates that an area or location is characterized by a specific type or classification of forest.
-
E.
hasHistoricKit
Indicates that an entity possesses or is associated with a historically significant version or design of a kit (e.g., uniform, equipment set, or standard set of items).
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 30, 2026, 11:59 p.m.