Triple
T19322606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isolde |
E483263
|
entity |
| Predicate | titleInLegend |
P135607
|
FINISHED |
| Object | princess |
—
|
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: princess | Statement: [Isolde, titleInLegend, princess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInLegend Context triple: [Isolde, titleInLegend, princess]
-
A.
titleOnTheLine
Indicates that a title or heading is positioned directly on a specific line (such as a line of text, a boundary, or a graphical line) rather than above, below, or separate from it.
-
B.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
C.
titleAffirms
Indicates that a title explicitly asserts, confirms, or supports the truth or validity of a particular claim, idea, or relationship.
-
D.
titleInLanguage
Indicates that a specific title or name is expressed in a particular language.
-
E.
title
Indicates that one entity serves as the formal name or designation of 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d8948948190b76a384041333509 |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4e4709d4481908c280cdd2ac18977 |
completed | April 19, 2026, 2:19 p.m. |
Created at: April 10, 2026, 1:32 p.m.