Triple
T27378001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Crawford |
E691131
|
entity |
| Predicate | historicallyHeldLandsIn |
P182343
|
FINISHED |
| Object | Angus |
—
|
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: Angus | Statement: [Earl of Crawford, historicallyHeldLandsIn, Angus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyHeldLandsIn Context triple: [Earl of Crawford, historicallyHeldLandsIn, Angus]
-
A.
landsPreviouslyBelongedTo
Indicates that the specified lands were owned, controlled, or possessed by a different party at an earlier time.
-
B.
hasHistoricLandGrants
Indicates that an entity has been granted land through one or more historically significant official land grants.
-
C.
landholdings
Indicates the extent or collection of land owned, controlled, or held by an entity.
-
D.
historicallyPartOf
Indicates that one entity was formerly a component, region, or subdivision of another entity during a past historical period, but is not necessarily part of it in the present.
-
E.
lordshipHeldIn
chosen
Indicates that an entity holds or exercises lordship, authority, or feudal control within a specified place or territorial jurisdiction.
- 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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 27, 2026, 12:21 p.m.