Triple
T34759071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pugliese torpedo defense system |
E1002014
|
entity |
| Predicate | firstAppliedOn |
—
|
GENERATED |
| Object | Littorio (battleship) |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAppliedOn Context triple: [Pugliese torpedo defense system, firstAppliedOn, Littorio (battleship)]
-
A.
firstAppliedTo
chosen
Indicates that an action, process, or treatment was initially used on or directed toward a particular entity before any others.
-
B.
appliedSince
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
C.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
D.
appliedBefore
Indicates that one action, process, or condition was applied earlier in time than another.
-
E.
firstPerformedOn
Indicates the date or occasion on which an action, event, or performance was carried out for the first time on a particular subject or object.
- F. None of above.
Provenance (1 batch)
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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.