Triple
T31418460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kroon |
E801463
|
entity |
| Predicate | hasPossibleOriginMeaning |
P15774
|
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: [Kroon, hasPossibleOriginMeaning, crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPossibleOriginMeaning Context triple: [Kroon, hasPossibleOriginMeaning, crown]
-
A.
hasMeaningInOriginLanguage
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning in its original or source language.
-
B.
hasMeaningByDerivation
Indicates that the meaning of one entity is obtained or derived from another entity, rather than being original or independent.
-
C.
hasLikelyOrigin
Indicates that one entity is inferred or believed, with some degree of uncertainty, to be the source or starting point of another entity.
-
D.
etymologyPossibleMeaning
chosen
Indicates a possible or hypothesized meaning that an etymological analysis suggests for a word or term.
-
E.
hasMultipleMeanings
Indicates that a term, symbol, or expression is associated with more than one distinct meaning or interpretation.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: April 30, 2026, 8:46 p.m.