Triple
T33980928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daring-class destroyer |
E871279
|
entity |
| Predicate | numberBuiltForRoyalAustralianNavy |
P205267
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Daring-class destroyer, numberBuiltForRoyalAustralianNavy, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberBuiltForRoyalAustralianNavy Context triple: [Daring-class destroyer, numberBuiltForRoyalAustralianNavy, 3]
-
A.
numberBuiltForRAF
Indicates the total quantity of items that were constructed specifically for use by the Royal Air Force.
-
B.
numberBuiltForRNZAF
Indicates the total quantity of items that were constructed specifically for the Royal New Zealand Air Force (RNZAF).
-
C.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
D.
navalClassNameInRoyalAustralianNavy
Indicates that a given naval class name is the designation used for that class within the Royal Australian Navy.
-
E.
numberOfWarPatrols
Indicates the count of distinct war patrol missions associated with an entity.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:50 a.m.