Triple
T36103948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opatija Riviera |
E1044297
|
entity |
| Predicate | historicalAs |
P65445
|
FINISHED |
| Object | Austro-Hungarian elite resort |
—
|
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: Austro-Hungarian elite resort | Statement: [Opatija Riviera, historicalAs, Austro-Hungarian elite resort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalAs Context triple: [Opatija Riviera, historicalAs, Austro-Hungarian elite resort]
-
A.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
B.
historicalSee
Indicates that one entity observed, encountered, or took visual notice of another entity in the past.
-
C.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
D.
historicFor
chosen
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
E.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0115fb84448190b8b67a5ace7b289a |
completed | May 10, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_6a0114ef60a081908f8db7868cf29b2f |
completed | May 10, 2026, 11:29 p.m. |
Created at: May 3, 2026, 4:08 p.m.