Triple
T27529543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battery Potter |
E694928
|
entity |
| Predicate | armamentMountType |
P52740
|
FINISHED |
| Object | disappearing carriage |
—
|
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: disappearing carriage | Statement: [Battery Potter, armamentMountType, disappearing carriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armamentMountType Context triple: [Battery Potter, armamentMountType, disappearing carriage]
-
A.
weaponMount
Indicates that one entity serves as a mounting point or support structure for attaching or holding a weapon on another entity.
-
B.
typeOfGunMount
chosen
Indicates the specific kind or configuration of gun mounting used to support or attach a gun.
-
C.
bayonetMount
Indicates that one object is equipped with or designed to accept a bayonet-style mounting connection to another object.
-
D.
primaryArmamentLayout
Indicates how the main weapons or primary armament of an entity are arranged or distributed relative to that entity.
-
E.
armamentCapacity
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f31e12c8190880b758fef6a07e0 |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:25 p.m.