Triple
T35829425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diboll, Texas |
E1035749
|
entity |
| Predicate | primaryTreeResource |
P84920
|
FINISHED |
| Object | Southern yellow pine forests |
—
|
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: Southern yellow pine forests | Statement: [Diboll, Texas, primaryTreeResource, Southern yellow pine forests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTreeResource Context triple: [Diboll, Texas, primaryTreeResource, Southern yellow pine forests]
-
A.
primaryResourceType
Indicates the main or predominant type/category of resource associated with an entity or activity.
-
B.
mainTreeType
chosen
Indicates the predominant type of tree that characterizes or dominates a given area, object, or context.
-
C.
primaryCollectionOf
Indicates that one entity serves as the main or principal collection to which another entity primarily belongs or is associated.
-
D.
centralResource
Indicates that one entity functions as the primary or core resource upon which another entity depends or is organized.
-
E.
primaryResourceSought
Indicates that an entity is the main or principal resource being sought or requested in a given 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.