Triple
T36747391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovelady, Texas |
E907802
|
entity |
| Predicate | isLocatedInForestRegion |
P39061
|
FINISHED |
| Object | area near Davy Crockett National Forest |
—
|
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: area near Davy Crockett National Forest | Statement: [Lovelady, Texas, isLocatedInForestRegion, area near Davy Crockett National Forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInForestRegion Context triple: [Lovelady, Texas, isLocatedInForestRegion, area near Davy Crockett National Forest]
-
A.
locatedInForest
chosen
Indicates that an entity is situated within the boundaries of a forest.
-
B.
isForested
Indicates that an area or region is covered predominantly by forest or dense tree vegetation.
-
C.
partOfForestRegion
Indicates that one entity is a component or subdivision within a larger forest region.
-
D.
hasForestType
Indicates that an area or location is characterized by a specific type or classification of forest.
-
E.
hasNearbyForestType
Indicates that one entity is located close to, or in the vicinity of, a forest of a specified type.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 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: May 3, 2026, 4:12 p.m.