Triple
T33574534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lycka |
E859993
|
entity |
| Predicate | containsEarlyVersionOf |
P88000
|
FINISHED |
| Object | Hej gamle man! |
—
|
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: Hej gamle man! | Statement: [Lycka, containsEarlyVersionOf, Hej gamle man!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsEarlyVersionOf Context triple: [Lycka, containsEarlyVersionOf, Hej gamle man!]
-
A.
hasEarlierVersion
Indicates that one entity is an earlier or prior version of another entity in a version sequence.
-
B.
containsNewVersionOf
Indicates that one entity includes or embeds a newer version of another entity.
-
C.
previousVersionIncluded
chosen
Indicates that an earlier version of an entity was contained within, or formed part of, the current entity.
-
D.
isYoungerVersionOf
Indicates that one entity represents the same individual as another entity, but at an earlier, younger stage in their life.
-
E.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a002f0839fc8190a874d3b0d0826d7e |
completed | May 10, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a002eae7b6481909974b321e2789b7e |
completed | May 10, 2026, 7:07 a.m. |
Created at: May 1, 2026, 1:40 a.m.