Triple
T4927620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Up Helly Aa |
E110614
|
entity |
| Predicate | hasObjectUsed |
P8225
|
FINISHED |
| Object | Viking-style longship (galley) |
—
|
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: Viking-style longship (galley) | Statement: [Up Helly Aa, hasObjectUsed, Viking-style longship (galley)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObjectUsed Context triple: [Up Helly Aa, hasObjectUsed, Viking-style longship (galley)]
-
A.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
-
B.
hasHumanUse
chosen
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
C.
areUsedSince
Indicates that entities have been in use continuously starting from a specified point in time.
-
D.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
E.
hasAdjacentUse
Indicates that one entity is used or occurs directly next to another in space, time, or sequence.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7036d8e88190bc4be2975160da23 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.