Triple
T30368478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin P5M Marlin |
E772484
|
entity |
| Predicate | redesignatedVariant |
P169127
|
FINISHED |
| Object | P-5A |
—
|
NE NERFINISHED |
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: P-5A | Statement: [Martin P5M Marlin, redesignatedVariant, P-5A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redesignatedVariant Context triple: [Martin P5M Marlin, redesignatedVariant, P-5A]
-
A.
designVariant
Indicates that one entity is an alternative design or version derived from or related to another entity’s design.
-
B.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
C.
customizedVariantOf
Indicates that one entity is a modified or tailored version derived from another, preserving a core basis while introducing specific customizations.
-
D.
redesigned
Indicates that an entity has been modified or created anew in terms of its structure, appearance, or functionality, replacing a previous design.
-
E.
denotesVariantOf
Indicates that one entity is a variant or alternative form of another, typically sharing core identity or function with some differences.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682812b90819099d2ebb8bb2953b6 |
completed | May 2, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 7:59 p.m.