Triple
T2435559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venda |
E52951
|
entity |
| Predicate | GuthrieCode |
P18539
|
FINISHED |
| Object | S.21 |
—
|
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: S.21 | Statement: [Venda, GuthrieCode, S.21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GuthrieCode Context triple: [Venda, GuthrieCode, S.21]
-
A.
guthrieClassification
chosen
Indicates a categorization relationship where an entity is assigned a class or type according to the Guthrie classification system.
-
B.
FIPSCode
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
-
C.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
D.
railroadCodeFor
Indicates that a specific railroad code is assigned to or used to identify a particular railroad entity.
-
E.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.