Triple
T3733857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince |
E79131
|
entity |
| Predicate | canDenote |
P37164
|
FINISHED |
| Object | sovereign ruler of a principality |
—
|
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: sovereign ruler of a principality | Statement: [Prince, canDenote, sovereign ruler of a principality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canDenote Context triple: [Prince, canDenote, sovereign ruler of a principality]
-
A.
canAlsoIndicate
chosen
Indicates that something may additionally signify, represent, or serve as another meaning or function beyond its primary one.
-
B.
canOwn
Indicates that one entity is permitted or legally able to possess or hold ownership rights over another entity.
-
C.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
canDeclare
Indicates that one entity has the authority or ability to formally declare or announce something about another entity or situation.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb2457f08190a6b94e9895fced2c |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.