Triple
T553014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5 train |
E11881
|
entity |
| Predicate | divisionLetter |
P899
|
FINISHED |
| Object | A Division |
—
|
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: A Division | Statement: [5 train, divisionLetter, A Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionLetter Context triple: [5 train, divisionLetter, A Division]
-
A.
divisionTitle
chosen
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
B.
division
Indicates a relationship where one entity is separated or partitioned into parts, groups, or sections based on some criterion or operation.
-
C.
divisionAssociation
Indicates an organizational relationship where one entity functions as a division, branch, or sub-unit of another entity.
-
D.
dividedBetween
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
E.
divisionOrStructure
Indicates a relationship where one entity is an internal division, department, or structural subunit that is organizationally contained within another entity.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991b296481908cf27e1d1ec67052 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bc1f8c8190904356f3a8e801de |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.