Triple
T58596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Japanese Navy |
E1159
|
entity |
| Predicate | peakPersonnel |
P3346
|
FINISHED |
| Object | about 2,000,000 |
—
|
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: about 2,000,000 | Statement: [Imperial Japanese Navy, peakPersonnel, about 2,000,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPersonnel Context triple: [Imperial Japanese Navy, peakPersonnel, about 2,000,000]
-
A.
keyPerson
Indicates that a person plays a primary, central, or critically important role in relation to an organization, project, or entity.
-
B.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
-
C.
staffIncluded
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
-
D.
hasPerson
Indicates that an entity is associated with or includes a specific person.
-
E.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24c9057348190aa6692eeeae19569 |
completed | Feb. 28, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69a24ac7547c81909bb68f327cdb9158 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24c8fa20c8190aacc38e53d1f654c |
completed | Feb. 28, 2026, 2:01 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.