Triple
T32612917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guard No. 47 |
E833706
|
entity |
| Predicate | hasAlternativeTitleForm |
P180520
|
FINISHED |
| Object | Strážný č. 47 |
—
|
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: Strážný č. 47 | Statement: [Guard No. 47, hasAlternativeTitleForm, Strážný č. 47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeTitleForm Context triple: [Guard No. 47, hasAlternativeTitleForm, Strážný č. 47]
-
A.
haveAlternativeTitle
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
-
B.
hasAlternativeTitleCombination
Indicates that an entity is associated with one or more alternative titles considered together as a specific combination or set.
-
C.
hasAlternativeTitleStyle
chosen
Indicates that an entity is associated with an alternative stylistic form or variation of its title.
-
D.
hasAlternativeEditionTitle
Indicates that an entity has a different or variant title used in another edition of the same work.
-
E.
hasAlternateTitleRegion
Indicates that an entity has an alternate title that is specifically used or valid within a particular geographic region.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 1, 2026, 1:06 a.m.