Triple
T37662830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snow Golem |
E937753
|
entity |
| Predicate | canBeNamedWith |
P180495
|
FINISHED |
| Object | name tag |
—
|
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: name tag | Statement: [Snow Golem, canBeNamedWith, name tag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeNamedWith Context triple: [Snow Golem, canBeNamedWith, name tag]
-
A.
canBeNamed
chosen
Indicates that an entity is capable of being assigned or given a specific name or label.
-
B.
canBePartOfName
Indicates that one entity is capable of serving as a component or segment within the full name of another entity.
-
C.
isNamedAccordingTo
Indicates that one entity receives its name based on, or in accordance with, another entity, rule, or naming convention.
-
D.
canBeFormalName
Indicates that something is suitable or valid to be used as a formal or official name.
-
E.
canBeStandaloneName
Indicates that something is suitable to function independently as a complete, self-contained name without requiring additional qualifiers or context.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: May 3, 2026, 4:18 p.m.