Triple
T24369209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve |
E614284
|
entity |
| Predicate | meaningViaRootName |
P28428
|
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: [Steve, meaningViaRootName, crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningViaRootName Context triple: [Steve, meaningViaRootName, crown]
-
A.
semanticRootMeaning
chosen
Indicates the fundamental or core meaning that underlies a word, phrase, or expression in a semantic structure.
-
B.
codeNameMeaning
Indicates that one entity is the meaning, interpretation, or significance associated with another entity’s code name.
-
C.
meaningViaPatricia
Indicates that something’s meaning, interpretation, or understanding is conveyed, mediated, or determined through an intermediary named Patricia.
-
D.
meaningViaJoshua
Indicates that something is understood, interpreted, or conveyed through the perspective, explanation, or mediation of Joshua.
-
E.
hasBaseNameMeaning
Indicates that an entity’s base name carries or is associated with a particular meaning.
- 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2938994c081909730d1e02e823dfd |
completed | April 29, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:01 a.m.