Triple
T3346549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-class destroyer |
E70387
|
entity |
| Predicate | laidDownInPeriod |
P39919
|
FINISHED |
| Object | late 1930s |
—
|
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: late 1930s | Statement: [K-class destroyer, laidDownInPeriod, late 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laidDownInPeriod Context triple: [K-class destroyer, laidDownInPeriod, late 1930s]
-
A.
laidDownPeriod
chosen
Indicates the time period during which something was formally established, enacted, or set in place.
-
B.
laidDownEndYear
Indicates the year in which something that was previously established, enacted, or laid down (such as a rule, law, or policy) ceased to be in effect.
-
C.
laidDownAs
Indicates that one entity has been formally established, stipulated, or prescribed as a rule, principle, or condition for another.
-
D.
laidDownBy
Indicates that something was established, created, or set as a rule, principle, or foundation by a particular agent.
-
E.
laidDownDate
Indicates the date on which something (such as a rule, law, standard, or foundation) was formally established, set, or put in place.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1f4ff888190bf14b9b7fbe9bcee |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.