Triple
T31590798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 88 Surface-to-Ship Missile |
E806090
|
entity |
| Predicate | crewPerLauncher |
P30694
|
FINISHED |
| Object | multiple personnel |
—
|
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: multiple personnel | Statement: [Type 88 Surface-to-Ship Missile, crewPerLauncher, multiple personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewPerLauncher Context triple: [Type 88 Surface-to-Ship Missile, crewPerLauncher, multiple personnel]
-
A.
crewCount
chosen
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
-
B.
crewOnboard
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
C.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
D.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
-
E.
providedCrewForMissionType
Indicates that an entity supplied or assigned crew members specifically for a particular type or category of mission.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a82ff6f081909acb6c9ef7a1bcba |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:28 p.m.