Triple
T8010563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch Ard |
E186477
|
entity |
| Predicate | hasBankCharacteristic |
P80550
|
FINISHED |
| Object | largely forested shores |
—
|
LITERAL 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: largely forested shores | Statement: [Loch Ard, hasBankCharacteristic, largely forested shores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBankCharacteristic Context triple: [Loch Ard, hasBankCharacteristic, largely forested shores]
-
A.
hasFeatureOnBanknotes
Indicates that a particular feature, such as a design element or security mark, appears on one or more banknotes.
-
B.
hasBankType
Indicates that an entity is associated with or classified by a particular type or category of bank.
-
C.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
-
D.
hasLandmarkOnBank
Indicates that a landmark is located on the bank (shore or edge) of a geographic feature such as a river, lake, or canal.
-
E.
hasBanknotes
Indicates that an entity possesses or contains one or more banknotes.
- F. None of above. chosen
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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d70caf8819090a9f98025470c0d |
completed | March 31, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:19 p.m.