Triple
T10694658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waldemar |
E252102
|
entity |
| Predicate | approximateMeaning |
P81437
|
FINISHED |
| Object | famous ruler |
—
|
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: famous ruler | Statement: [Waldemar, approximateMeaning, famous ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateMeaning Context triple: [Waldemar, approximateMeaning, famous ruler]
-
A.
literalMeaningApproximation
chosen
Indicates that one entity expresses an approximate or rough literal meaning of another entity, rather than an exact or fully precise interpretation.
-
B.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
C.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
-
D.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
-
E.
logicalMeaning
Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd39c3788190bb7cd0acf8b6efdd |
completed | April 9, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:11 p.m.