Triple
T20718923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Eridge |
E509254
|
entity |
| Predicate | navalDisplacement |
P10289
|
FINISHED |
| Object | approximately 1000–1100 tons standard |
—
|
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: approximately 1000–1100 tons standard | Statement: [HMS Eridge, navalDisplacement, approximately 1000–1100 tons standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalDisplacement Context triple: [HMS Eridge, navalDisplacement, approximately 1000–1100 tons standard]
-
A.
standardDisplacement
chosen
Indicates the typical or officially specified amount of displacement (such as volume, weight, or capacity) associated with an entity under standard conditions.
-
B.
embarkedForcesCapacity
Indicates the maximum number of forces (e.g., troops or personnel) that can be embarked or carried by a given platform or unit.
-
C.
shipLength
Indicates the physical length measurement of a ship.
-
D.
dispositionOfShips
Indicates the arrangement, allocation, or positioning of ships relative to a plan, location, or situation.
-
E.
navalRating
Indicates the assessed level of naval strength, capability, or performance attributed to an entity.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d39bec8190b3642b0d6d833375 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:26 p.m.