Triple
T16803638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stevie |
E408421
|
entity |
| Predicate | meaningInheritedFromRoot |
P14723
|
FINISHED |
| Object | crown |
—
|
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: crown | Statement: [Stevie, meaningInheritedFromRoot, crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningInheritedFromRoot Context triple: [Stevie, meaningInheritedFromRoot, crown]
-
A.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
-
B.
semanticRootMeaning
Indicates the fundamental or core meaning that underlies a word, phrase, or expression in a semantic structure.
-
C.
isInherited
Indicates that one entity derives its characteristics, properties, or rights from another through an inheritance relationship.
-
D.
etymologicalRootMeaning
chosen
Indicates that one term’s meaning originates from or is derived from the historical or original meaning of another term.
-
E.
etymologicalRootName
Indicates that one name is derived from, or originates etymologically in, another name.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2ca46f88190b56e81d75012496c |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e319d0fdb8819088425bd82431640f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.