Triple
T16568160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DEFA 30 mm cannon family |
E402515
|
entity |
| Predicate | typicalFeedSystem |
P25552
|
FINISHED |
| Object | linkless feed |
—
|
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: linkless feed | Statement: [DEFA 30 mm cannon family, typicalFeedSystem, linkless feed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFeedSystem Context triple: [DEFA 30 mm cannon family, typicalFeedSystem, linkless feed]
-
A.
feedSystem
Indicates that one entity supplies or provides input, resources, or data into another entity or system for its operation or processing.
-
B.
mainFeederOf
Indicates that one entity serves as the primary source or supplier of resources, energy, or input to another entity.
-
C.
feederSystem
chosen
Indicates a system or mechanism that supplies or feeds resources, materials, or inputs into another process, component, or structure.
-
D.
feedsReservoir
Indicates that one entity supplies or channels a flow (such as water or another resource) into a reservoir.
-
E.
feedsViaAqueduct
Indicates that something supplies or channels a resource (typically water) to another thing through an aqueduct.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35772f6608190a125c7d3c199c3e2 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.