Triple
T37615273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearly Prince |
E935902
|
entity |
| Predicate | hasParentTitle |
P149892
|
FINISHED |
| Object | Pearly King |
—
|
NE NERFINISHED |
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: Pearly King | Statement: [Pearly Prince, hasParentTitle, Pearly King]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentTitle Context triple: [Pearly Prince, hasParentTitle, Pearly King]
-
A.
hasParentWithTitle
chosen
Indicates that an entity has at least one parent who holds a specified title or formal designation.
-
B.
hasAncestralTitle
Indicates that an entity holds or is associated with a hereditary or historically inherited title passed down through ancestry.
-
C.
hasTitleInFamily
Indicates that one entity holds a specific familial title or role in relation to another entity within a family context.
-
D.
parentTitle
Indicates that one entity has a title that is the parent or higher-level title of another entity’s title in a hierarchical structure.
-
E.
hasTitleFrom
Indicates that one entity holds or uses a title that originates from, or is conferred by, another entity.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
Created at: May 3, 2026, 4:18 p.m.