Triple
T38429388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fraser of Philorth |
E903755
|
entity |
| Predicate | hasHereditaryLands |
P90583
|
FINISHED |
| Object | Philorth estate |
—
|
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: Philorth estate | Statement: [Fraser of Philorth, hasHereditaryLands, Philorth estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHereditaryLands Context triple: [Fraser of Philorth, hasHereditaryLands, Philorth estate]
-
A.
hasAncestralLandsOf
Indicates that one entity possesses or is traditionally associated with the ancestral lands belonging to another entity.
-
B.
hasAncestralLand
chosen
Indicates that an entity possesses land inherited from its ancestors or traditionally associated with its lineage.
-
C.
hasHereditaryLegacy
Indicates that an entity possesses a legacy, status, or attribute that is passed down through familial or ancestral inheritance.
-
D.
hasHereditaryRights
Indicates that one entity possesses rights or privileges that are passed down through family lineage or inheritance from another entity.
-
E.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:31 p.m.