Triple
T38556379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukedom of Fife |
E925255
|
entity |
| Predicate | notableResidenceAssociated |
P57645
|
FINISHED |
| Object | Mar Lodge |
E2203871
|
NE 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: Mar Lodge | Statement: [Dukedom of Fife, notableResidenceAssociated, Mar Lodge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableResidenceAssociated Context triple: [Dukedom of Fife, notableResidenceAssociated, Mar Lodge]
-
A.
hasFamousResidence
Indicates that an entity is associated with a residence that is widely recognized or notable.
-
B.
notableBuildingAssociated
chosen
Indicates a relationship where a notable or significant building is associated with, connected to, or relevant to a given entity.
-
C.
servedAsResidenceOf
Indicates that something functioned as the home or dwelling place of a particular person or group.
-
D.
residenceAssociatedWithOffice
Indicates a relationship where a residence is connected or linked to a particular office, such as being located at, attached to, or officially designated for that office.
-
E.
hasNotableResident
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
- F. None of above.
Provenance (4 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41e0418274819088dfdc4c8c0f7190 |
completed | June 29, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.