Triple
T2873172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Warspite |
E56812
|
entity |
| Predicate | scrappingLocation |
P43448
|
FINISHED |
| Object | near Penzance, Cornwall (wrecked en route to breakers) |
—
|
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: near Penzance, Cornwall (wrecked en route to breakers) | Statement: [HMS Warspite, scrappingLocation, near Penzance, Cornwall (wrecked en route to breakers)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scrappingLocation Context triple: [HMS Warspite, scrappingLocation, near Penzance, Cornwall (wrecked en route to breakers)]
-
A.
recruitmentLocation
Indicates the place or geographic area where the recruitment or hiring of individuals occurs.
-
B.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
C.
featuresLocation
Indicates that something is characterized by or includes a specific location as one of its notable attributes.
-
D.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
E.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
- F. None of above. chosen
Provenance (4 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abdfe59ef88190b8bdfdd03e8965f3 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:03 p.m.