Triple
T4539724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Phillips |
E107496
|
entity |
| Predicate | hasNoRoyalTitle |
P57574
|
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: [Peter Phillips, hasNoRoyalTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoRoyalTitle Context triple: [Peter Phillips, hasNoRoyalTitle, true]
-
A.
hasNotableDukedom
Indicates that an entity holds or is associated with a dukedom that is considered historically or culturally significant.
-
B.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
C.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
D.
isNotPeerage
Indicates that the entity does not belong to any recognized peerage or noble rank within a hierarchical social or nobility system.
-
E.
hasRoyalConnection
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
- 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57ba327c8190a7f12e14077b1fa7 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:04 p.m.