Triple
T25888269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London District |
E652253
|
entity |
| Predicate | hasTypeOfAreaManaged |
P48713
|
FINISHED |
| Object | federal forest land |
—
|
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: federal forest land | Statement: [London District, hasTypeOfAreaManaged, federal forest land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfAreaManaged Context triple: [London District, hasTypeOfAreaManaged, federal forest land]
-
A.
hasManagementArea
Indicates that one entity is responsible for managing, overseeing, or administering a specified area or region.
-
B.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
C.
hasTypeOfManagement
Indicates that an entity is associated with or operates under a specified form or style of management.
-
D.
typeOfJurisdictionManaged
chosen
Indicates the specific kind or category of jurisdiction that an entity is responsible for managing or overseeing.
-
E.
hasStudyAreaType
Indicates that an entity’s study area is classified as a specific type or category (e.g., lab, field site, classroom).
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 22, 2026, 8:18 a.m.