Triple
T8445878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lour, Angus |
E199673
|
entity |
| Predicate | hasHistoricLandUse |
P44099
|
FINISHED |
| Object | country estate |
—
|
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: country estate | Statement: [Lour, Angus, hasHistoricLandUse, country estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricLandUse Context triple: [Lour, Angus, hasHistoricLandUse, country estate]
-
A.
hasHistoricalLandCover
Indicates that an entity is associated with information about the land cover that existed in a specified area during a past time period.
-
B.
formerLandUse
chosen
Indicates the type of land use that characterized a location prior to its current or present use.
-
C.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
-
D.
hasHistoricVillageArea
Indicates that an entity includes or is associated with an area recognized as a historic village or traditional settlement zone.
-
E.
hasHistoricLandGrants
Indicates that an entity has been granted land through one or more historically significant official land grants.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe3152a3c819092efdeab718def7a |
completed | March 31, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.