Triple
T37811818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess of Mar |
E942665
|
entity |
| Predicate | canBeHeldSuoJure |
P200538
|
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: [Countess of Mar, canBeHeldSuoJure, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeHeldSuoJure Context triple: [Countess of Mar, canBeHeldSuoJure, yes]
-
A.
canBeHeld
Indicates that an entity is capable of being physically grasped, supported, or carried by another entity.
-
B.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
-
C.
mayBeHeldAs
Indicates that one entity can potentially be possessed, owned, or kept by another entity, without asserting that this possession actually occurs.
-
D.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
E.
canBeHeldIn
Indicates that one entity is capable of being contained, hosted, or conducted within another entity.
- F. None of above. chosen
Provenance (4 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
| PDg | Predicate description generation | batch_69ff935f48808190aa6f4834f59d45b8 |
completed | May 9, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.