Triple
T5191774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Norway |
E117171
|
entity |
| Predicate | cannotBeHeldBy |
P61996
|
FINISHED |
| Object | a man |
—
|
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: a man | Statement: [Queen of Norway, cannotBeHeldBy, a man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeHeldBy Context triple: [Queen of Norway, cannotBeHeldBy, a man]
-
A.
notAutomaticallyHeldBy
Indicates that a particular right, status, or condition is not granted or possessed by default and must be explicitly obtained or established.
-
B.
isUsuallyHeldBy
Indicates that something is most commonly or typically possessed, carried, or controlled by a particular entity.
-
C.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
D.
automaticallyHeld
Indicates that the holding or possession relationship occurs by default or system rule, without requiring an explicit action or decision by the involved entities.
-
E.
notHeldDuring
Indicates that a specified condition, event, or relationship does not occur or is not in effect throughout a given time interval or temporal context.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79ed61c88190bda492f6489f44de |
completed | March 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78d6a1388190804dcf568ca92129 |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:46 p.m.