Triple
T29058043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayumi |
E735444
|
entity |
| Predicate | hasMeaningVariant |
P148903
|
FINISHED |
| Object | “true bow” |
—
|
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 bow” | Statement: [Mayumi, hasMeaningVariant, “true bow”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeaningVariant Context triple: [Mayumi, hasMeaningVariant, “true bow”]
-
A.
hasMultipleMeanings
Indicates that a term, symbol, or expression is associated with more than one distinct meaning or interpretation.
-
B.
hasMeaningInOriginLanguage
chosen
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning in its original or source language.
-
C.
hasMeaningExtension
Indicates that one entity represents an extended, elaborated, or more detailed meaning of another entity’s meaning.
-
D.
hasVariantSpelling
Indicates that one term is an alternative spelling form of another term.
-
E.
hasVariantReadingsWith
Indicates a relationship where two textual items are linked because they exhibit differing or alternative readings of (typically) the same underlying content.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 28, 2026, 10:13 a.m.