Triple
T9006317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M113 armoured personnel carrier |
E215150
|
entity |
| Predicate | isAmphibious |
P32308
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [M113 armoured personnel carrier, isAmphibious, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAmphibious Context triple: [M113 armoured personnel carrier, isAmphibious, yes]
-
A.
hasAmphibiousCapability
chosen
Indicates that an entity possesses the ability to operate effectively in both water and land environments.
-
B.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
-
C.
hasSeaArmType
Indicates that an entity is associated with or characterized by a specific type of sea arm (such as a bay, gulf, fjord, or similar marine inlet).
-
D.
hasSubmersibleBridge
Indicates that one entity possesses or includes a bridge structure designed to be lowered or submerged, typically to allow passage over or through water.
-
E.
designedToEmbark
Indicates that something is created or configured with the specific purpose of beginning or initiating a journey, process, or undertaking.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc69bc6e208190b0c01e3761c04799 |
completed | April 1, 2026, 12:41 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.