Triple
T27092705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelia |
E686211
|
entity |
| Predicate | hasLinguisticRootMeaning |
P28428
|
FINISHED |
| Object | noble |
—
|
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: noble | Statement: [Adelia, hasLinguisticRootMeaning, noble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLinguisticRootMeaning Context triple: [Adelia, hasLinguisticRootMeaning, noble]
-
A.
hasMeaningInOriginLanguage
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning in its original or source language.
-
B.
hasRootWord
Indicates that one linguistic form is derived from, based on, or directly associated with a specified root word.
-
C.
hasMeaningByDerivation
Indicates that the meaning of one entity is obtained or derived from another entity, rather than being original or independent.
-
D.
semanticRootMeaning
chosen
Indicates the fundamental or core meaning that underlies a word, phrase, or expression in a semantic structure.
-
E.
linguisticallyRelatedTo
Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 27, 2026, 8:41 a.m.