Triple
T8965101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess of Gloucester |
E214109
|
entity |
| Predicate | typicalHolderConnection |
P5651
|
FINISHED |
| Object | royal family |
—
|
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: royal family | Statement: [Countess of Gloucester, typicalHolderConnection, royal family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHolderConnection Context triple: [Countess of Gloucester, typicalHolderConnection, royal family]
-
A.
isUsuallyHeldBy
chosen
Indicates that something is most commonly or typically possessed, carried, or controlled by a particular entity.
-
B.
typicallyHolds
Indicates that a certain relationship or condition generally holds true in typical or normal situations, though not necessarily in all cases.
-
C.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
D.
holderService
Indicates that one entity provides or is responsible for a service on behalf of another entity that holds or owns it.
-
E.
circuitHolding
Indicates that one entity is physically grasping, supporting, or maintaining control of an electrical circuit or circuit component.
- 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc674c4be8819090d46aba8ab40af3 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:01 p.m.