Triple
T32241251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Taejon |
E823618
|
entity |
| Predicate | NKUnit |
P173873
|
FINISHED |
| Object | 3rd Infantry Division |
—
|
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: 3rd Infantry Division | Statement: [Battle of Taejon, NKUnit, 3rd Infantry Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NKUnit Context triple: [Battle of Taejon, NKUnit, 3rd Infantry Division]
-
A.
testCase
Indicates a relationship where a specific scenario, input set, or condition is used to verify, validate, or evaluate the behavior or correctness of a system, component, or function.
-
B.
testSuite
Indicates that one entity is a collection or grouping of tests designed to be executed together, typically to validate behavior or functionality.
-
C.
commonTest
Indicates that two or more entities share the same test, testing procedure, or evaluation in common.
-
D.
sampleSuite
Indicates that an entity is part of, associated with, or belongs to a particular sample suite (a grouped set of related samples or tests).
-
E.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
- 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc30303081909c6842161ec2df46 |
completed | May 3, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:40 a.m.