Triple
T31507308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAE Systems Submarines |
E803852
|
entity |
| Predicate | constructsFor |
P80317
|
FINISHED |
| Object | Royal Navy |
—
|
NE NERFINISHED |
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: Royal Navy | Statement: [BAE Systems Submarines, constructsFor, Royal Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructsFor Context triple: [BAE Systems Submarines, constructsFor, Royal Navy]
-
A.
constructs
Indicates that an agent builds, creates, or assembles something, typically resulting in a new or more complex entity or structure.
-
B.
coreConstruct
Indicates a fundamental building or organizing relationship where one entity serves as the essential basis or primary component from which another entity is formed or structured.
-
C.
constructedTo
chosen
Indicates that one entity has been built, created, or designed for the purpose of serving, supporting, or enabling another entity.
-
D.
originalConstructionFor
Indicates that one entity was the initial or first-built structure, design, or form intended for use by another entity.
-
E.
canBeConstructedWith
Indicates that one entity can be formed, built, or assembled using another entity as material, components, or means.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 30, 2026, 9:48 p.m.