Triple
T31275527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Publication 5-0, Joint Planning |
E797505
|
entity |
| Predicate | hasJPNumber |
P171531
|
FINISHED |
| Object | JP 5-0 |
—
|
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: JP 5-0 | Statement: [Joint Publication 5-0, Joint Planning, hasJPNumber, JP 5-0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJPNumber Context triple: [Joint Publication 5-0, Joint Planning, hasJPNumber, JP 5-0]
-
A.
eraNumberInJapan
Indicates the specific numbered position of a historical era within the sequence of Japanese eras.
-
B.
hasJISRouteNumber
Indicates that an entity is assigned a specific route number according to the JIS (Japanese Industrial Standards) route numbering system.
-
C.
hasJapaneseText
Indicates that an entity contains or is associated with text written in the Japanese language.
-
D.
hasNameInJapanese
Indicates that an entity is associated with a specific name expressed in the Japanese language.
-
E.
hasJapaneseSurname
Indicates that the person or entity possesses a surname that is of Japanese origin or is commonly used in Japanese naming conventions.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 29, 2026, 9:13 p.m.