Triple
T2480089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese National Railways |
E55792
|
entity |
| Predicate | hadEmployeeCount |
P17907
|
FINISHED |
| Object | over 400000 employees at peak |
—
|
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: over 400000 employees at peak | Statement: [Japanese National Railways, hadEmployeeCount, over 400000 employees at peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadEmployeeCount Context triple: [Japanese National Railways, hadEmployeeCount, over 400000 employees at peak]
-
A.
hasEmployees
Indicates that one entity employs one or more other entities as its workers or staff.
-
B.
employsApproximateNumberOfPeople
chosen
Indicates that an entity employs a roughly estimated or approximate number of people, rather than an exact headcount.
-
C.
staffSize
Indicates the number of staff members associated with an entity.
-
D.
hasNumberOfCompanies
Indicates the quantitative relationship specifying how many companies are associated with a given entity.
-
E.
employedApproximately
Indicates that one entity employs another in a manner where the number, duration, or extent of employment is approximate rather than exact.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.