Triple
T9701713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marlborough dukedom |
E234792
|
entity |
| Predicate | hasSpecialRemainder |
P30432
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Marlborough dukedom, hasSpecialRemainder, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialRemainder Context triple: [Marlborough dukedom, hasSpecialRemainder, yes]
-
A.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
B.
hasRemainsOf
Indicates that one entity physically contains, preserves, or is associated with the leftover physical traces or remnants of another entity.
-
C.
hasSpecialRules
chosen
Indicates that certain entities are governed by additional or exceptional rules that differ from the standard ones.
-
D.
hasSpecialCategory
Indicates that an entity is associated with a designated special or exceptional category distinct from its standard classifications.
-
E.
hasSpecials
Indicates that an entity offers or is associated with special deals, promotions, or limited-time offers.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d70f55c8190934f37c25e9d4ba4 |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:18 p.m.