Triple
T30060119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nobuko |
E763850
|
entity |
| Predicate | commonSuffixMeaning |
P180492
|
FINISHED |
| Object | child |
—
|
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: child | Statement: [Nobuko, commonSuffixMeaning, child]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonSuffixMeaning Context triple: [Nobuko, commonSuffixMeaning, child]
-
A.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
B.
etymologySuffix
Indicates that one term functions as a suffix in the etymological formation or derivation of another term.
-
C.
commonMeaningElement
chosen
Indicates that multiple items share a common semantic component or conceptual element in their meanings.
-
D.
usedAsSuffixTo
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
-
E.
typicalMeaning
Indicates that something represents the usual, characteristic, or most common meaning or interpretation associated with something else.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 29, 2026, 6:57 p.m.