Triple
T26747980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medway Queen |
E674453
|
entity |
| Predicate | majorHullRebuildCompleted |
P13529
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Medway Queen, majorHullRebuildCompleted, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorHullRebuildCompleted Context triple: [Medway Queen, majorHullRebuildCompleted, 2013]
-
A.
rebuiltCompletedIn
Indicates that an entity has undergone a rebuilding process that was fully completed in a specified time or event.
-
B.
largelyRebuilt
Indicates that an entity has been substantially reconstructed or renovated, with most of its original structure replaced or significantly altered.
-
C.
majorRebuildCompleted
chosen
Indicates that a significant reconstruction or overhaul of an entity has been fully completed.
-
D.
notableShipRepaired
Indicates that an entity is recognized for having repaired a ship of particular significance or notability.
-
E.
hasMajorReconstruction
Indicates that an entity has undergone a significant or extensive reconstruction or renovation.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 27, 2026, 3:52 a.m.