Triple
T7385461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seigneur of Sark |
E170367
|
entity |
| Predicate | hasHistoricalRight |
P15548
|
FINISHED |
| Object | monopoly on milling |
—
|
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: monopoly on milling | Statement: [Seigneur of Sark, hasHistoricalRight, monopoly on milling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalRight Context triple: [Seigneur of Sark, hasHistoricalRight, monopoly on milling]
-
A.
historicalRightGranted
chosen
Indicates that a right or privilege was formally granted to an entity at some point in the past.
-
B.
hasHistoricalSection
Indicates that something includes a dedicated part or segment that presents historical information or context.
-
C.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
-
D.
hasHistoricalSeat
Indicates that an entity possesses or is associated with a historically significant seat, location, or place of authority.
-
E.
hasHistoricalRoleAs
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1f117ec8190a97cbd0b35d5811a |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:08 p.m.