Triple
T27235798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permanent School Fund |
E682266
|
entity |
| Predicate | landManagedBy |
P124439
|
FINISHED |
| Object | Texas General Land Office |
—
|
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: Texas General Land Office | Statement: [Permanent School Fund, landManagedBy, Texas General Land Office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landManagedBy Context triple: [Permanent School Fund, landManagedBy, Texas General Land Office]
-
A.
onLandManagedBy
chosen
Indicates that something is located on land that is administered, controlled, or overseen by a particular managing entity.
-
B.
boundaryManagedBy
Indicates that the defined boundary is overseen, controlled, or administered by a specific managing entity.
-
C.
isOnIslandManagedBy
Indicates that one entity is located on an island that is administered or overseen by another entity.
-
D.
laterManagedBy
Indicates that an entity was, at a subsequent time, managed or overseen by another entity.
-
E.
landManagement
Indicates how land is planned, used, and controlled over time, including decisions about its conservation, development, and resource use.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6267913848190bbdc065a215cae22 |
completed | May 2, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:47 a.m.