Triple
T14267888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Supply |
E353697
|
entity |
| Predicate | laidUp |
P113502
|
FINISHED |
| Object | after return to England |
—
|
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: after return to England | Statement: [HMS Supply, laidUp, after return to England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laidUp Context triple: [HMS Supply, laidUp, after return to England]
-
A.
laidDown
Indicates that an entity places or sets another entity down into a resting or horizontal position.
-
B.
laidBy
Indicates that one entity produced or deposited another entity, typically referring to an egg or similar object being laid by its source.
-
C.
keelLaidFor
Indicates that the initial structural construction (keel laying) of a vessel has been formally started for a particular ship or project.
-
D.
laidDownBy
Indicates that something was established, created, or set as a rule, principle, or foundation by a particular agent.
-
E.
laidDownAs
Indicates that one entity has been formally established, stipulated, or prescribed as a rule, principle, or condition for another.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6358c2288190ac1fd26e688a605d |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:10 a.m.