Triple
T10303079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrystal |
E241680
|
entity |
| Predicate | hasSemanticAssociation |
P12753
|
FINISHED |
| Object | crystal |
—
|
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: crystal | Statement: [Chrystal, hasSemanticAssociation, crystal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSemanticAssociation Context triple: [Chrystal, hasSemanticAssociation, crystal]
-
A.
hasSemanticsDefinedBy
Indicates that the meaning or interpretation of one entity is specified, constrained, or determined by another entity.
-
B.
semanticRelation
chosen
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
C.
hasSemantics
Indicates that one entity carries or encodes the meaning, interpretation, or semantic content associated with another entity.
-
D.
hasLexicalInfluenceOn
Indicates that one linguistic element (such as a word, phrase, or lexicon) has affected or shaped the form, usage, or meaning of another linguistic element.
-
E.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d30846108190875042ab1c0204e0 |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:45 a.m.