Triple
T30109614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountbatten-Windsor |
E765228
|
entity |
| Predicate | notUsuallyUsedAs |
P7974
|
FINISHED |
| Object | regnal name |
—
|
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: regnal name | Statement: [Mountbatten-Windsor, notUsuallyUsedAs, regnal name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notUsuallyUsedAs Context triple: [Mountbatten-Windsor, notUsuallyUsedAs, regnal name]
-
A.
notTypicallyUsedFor
chosen
Indicates that something is generally not used for a particular purpose, function, or activity under normal circumstances.
-
B.
notUsedOver
Indicates that one entity has not been used, applied, or utilized for a duration exceeding a specified time period relative to another entity or reference point.
-
C.
notTypically
Indicates that the referenced situation, behavior, or relationship does not usually or normally occur under standard or expected conditions.
-
D.
notUsedAt
Indicates that a particular entity is not utilized, applied, or active at a specified location, time, or context.
-
E.
usedLessIn
Indicates that one entity is used with a lower frequency or intensity compared to 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67dbea60881908c1877527d877ba0 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:10 p.m.