Triple
T35531367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baelish of the Fingers |
E1026807
|
entity |
| Predicate | landholdingLocation |
P113753
|
FINISHED |
| Object | the Fingers |
—
|
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: the Fingers | Statement: [Baelish of the Fingers, landholdingLocation, the Fingers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landholdingLocation Context triple: [Baelish of the Fingers, landholdingLocation, the Fingers]
-
A.
landholdings
Indicates the extent or collection of land owned, controlled, or held by an entity.
-
B.
landholderIn
Indicates that one entity holds legal or recognized ownership or tenancy rights over land located within the jurisdiction or bounds of another entity.
-
C.
hasLandholdingsIn
chosen
Indicates that an entity owns or controls land or property located within a specified geographic area.
-
D.
landGrantLocation
Indicates the geographic place or area to which a particular land grant applies or in which it is situated.
-
E.
ownedLandBy
Indicates that one entity possesses legal or recognized ownership rights over a piece or area of land associated with another entity.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.