Triple
T8218637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fork-tailed Devil |
E192001
|
entity |
| Predicate | armamentLocation |
P22939
|
FINISHED |
| Object | nose-mounted guns |
—
|
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: nose-mounted guns | Statement: [Fork-tailed Devil, armamentLocation, nose-mounted guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armamentLocation Context triple: [Fork-tailed Devil, armamentLocation, nose-mounted guns]
-
A.
armamentStations
chosen
Indicates a relationship where specific locations or mounts on a platform (such as a vehicle, vessel, or structure) are designated for installing or carrying weapons or armaments.
-
B.
armamentCapacity
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
-
C.
armamentStatus
Indicates the current condition or readiness level of an entity’s weapons or military equipment.
-
D.
armamentWWII
Indicates that an entity served as a weapon, piece of equipment, or military hardware used during World War II.
-
E.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb7770cee881908ade560d49427895 |
completed | March 31, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:45 p.m.