Triple
T2969468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ES-MD |
E80245
|
entity |
| Predicate | secondPartType |
P30246
|
FINISHED |
| Object | two-letter code |
—
|
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: two-letter code | Statement: [ES-MD, secondPartType, two-letter code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondPartType Context triple: [ES-MD, secondPartType, two-letter code]
-
A.
secondPartSubject
Indicates that the referenced entity serves as the second part or component of the subject in a composite or multipart relationship.
-
B.
secondStageType
Indicates the specific kind or category of a process, object, or event that occurs as the second stage in a multi-stage sequence.
-
C.
secondPartTitle
Indicates that one entity is the second part of the title of another entity.
-
D.
secondPartFormat
chosen
Indicates that the entity represents the format or structure of the second part or segment of a larger item or sequence.
-
E.
secondParty
Indicates that an entity participates in a relationship or transaction as the second party relative to a primary (first) party.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9970e2c08190affa5efedb9aad75 |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.