Triple
T30117340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Grey, 3rd Earl of Kent |
E765455
|
entity |
| Predicate | ancestralLandsLocation |
P90583
|
FINISHED |
| Object | Kent |
—
|
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: Kent | Statement: [Richard Grey, 3rd Earl of Kent, ancestralLandsLocation, Kent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestralLandsLocation Context triple: [Richard Grey, 3rd Earl of Kent, ancestralLandsLocation, Kent]
-
A.
associatedTribeLocation
Indicates a relationship where a tribe is linked or connected to a specific geographic location.
-
B.
hasAncestralLand
chosen
Indicates that an entity possesses land inherited from its ancestors or traditionally associated with its lineage.
-
C.
cultLocation
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
-
D.
hasNearbyTribalLand
Indicates that an entity is located close to or adjacent to land officially recognized as belonging to a tribal nation or indigenous community.
-
E.
notableExpeditionLocation
Indicates that a location is a significant or primary place associated with a particular expedition.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67de83980819098ac89078e1d75d6 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:12 p.m.