Triple
T16424217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M47 Patton |
E398895
|
entity |
| Predicate | turretOrigin |
P122730
|
FINISHED |
| Object | new turret design with stereoscopic rangefinder |
—
|
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: new turret design with stereoscopic rangefinder | Statement: [M47 Patton, turretOrigin, new turret design with stereoscopic rangefinder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turretOrigin Context triple: [M47 Patton, turretOrigin, new turret design with stereoscopic rangefinder]
-
A.
turretPlacement
Indicates the spatial or positional relationship defining where a turret is placed relative to its environment or reference objects.
-
B.
turret
Indicates that an entity is equipped with or associated with a turret, typically a rotating weapon or defense mechanism.
-
C.
turretBasedOn
Indicates that one turret is derived from, modeled after, or constructed using the design or components of another turret.
-
D.
turretCount
Indicates the number of turrets associated with or mounted on a given entity.
-
E.
turretTraverse
Indicates the action or capability of a turret rotating horizontally to change its aiming direction.
- F. None of above. chosen
Provenance (4 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328f9da9081908dadbdac4b2d38ec |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.