Triple
T48843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero of Socialist Labour |
E959
|
entity |
| Predicate | entailsTitle |
P1116
|
FINISHED |
| Object | Hero of Socialist Labour of the USSR |
—
|
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: Hero of Socialist Labour of the USSR | Statement: [Hero of Socialist Labour, entailsTitle, Hero of Socialist Labour of the USSR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entailsTitle Context triple: [Hero of Socialist Labour, entailsTitle, Hero of Socialist Labour of the USSR]
-
A.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
B.
longTitle
chosen
Indicates that an entity has an extended or full-length title associated with it.
-
C.
hasTitleHolder
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
D.
hasSubsidiaryTitle
Indicates that an entity has an additional or secondary title formally associated with its main title.
-
E.
hasGenderedTitle
Indicates that an entity is associated with a title or form of address that is explicitly marked for a particular gender.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abfa7bc8190932c137a823efcb6 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.