Triple
T21958881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi A7M Reppū |
E542266
|
entity |
| Predicate | prototypeCountApproximate |
P146706
|
FINISHED |
| Object | few prototypes built |
—
|
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: few prototypes built | Statement: [Mitsubishi A7M Reppū, prototypeCountApproximate, few prototypes built]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prototypeCountApproximate Context triple: [Mitsubishi A7M Reppū, prototypeCountApproximate, few prototypes built]
-
A.
mineCountApproximate
Indicates that the number of mines associated with an entity is estimated or roughly counted rather than known exactly.
-
B.
lapCountApproximate
Indicates that the recorded number of laps is an estimate rather than an exact, precise count.
-
C.
hasApproximateBrickCount
Indicates that an entity is associated with an estimated or non-exact number of bricks.
-
D.
hasApproximateMemberCount
Indicates that an entity is associated with a group or collection for which only an estimated or non-exact number of members is known.
-
E.
hasApproximateEntryCount
Indicates that an entity is associated with a number representing an estimated or non-exact count of its entries.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1244204f081909742d4fe138610d6 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb9b75308190addc3dba7b5d5ddd |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 8 p.m.