Triple
T3778399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baronetage of the United Kingdom |
E83361
|
entity |
| Predicate | canBecomeDormant |
P17096
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Baronetage of the United Kingdom, canBecomeDormant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBecomeDormant Context triple: [Baronetage of the United Kingdom, canBecomeDormant, true]
-
A.
isDormant
chosen
Indicates that an entity is currently inactive or in a resting state, with its usual functions or activities temporarily suspended.
-
B.
canBeVacantWhen
Indicates the conditions or circumstances under which something is allowed or able to remain unoccupied or empty.
-
C.
isPotentiallyActive
Indicates that an entity has the capacity or conditions to become active, but is not necessarily active at the present moment.
-
D.
canExpire
Indicates that the subject has the property or status of being able to end, lapse, or become invalid after a certain time or condition is met.
-
E.
canBeDisabledOn
Indicates that a feature, function, or capability has the property that it can be turned off or deactivated when applied to the referenced 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc78173081908b230017834cdf9e |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.