Triple
T9068702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Standard Recording Code |
E217307
|
entity |
| Predicate | countryCodeLength |
P86779
|
FINISHED |
| Object | 2 characters |
—
|
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: 2 characters | Statement: [International Standard Recording Code, countryCodeLength, 2 characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCodeLength Context triple: [International Standard Recording Code, countryCodeLength, 2 characters]
-
A.
countryCodeFormat
Indicates the standardized structure or pattern in which a country's code must be represented.
-
B.
countryCodePart
Indicates that one entity is a segment or component of a standardized country code associated with another entity.
-
C.
UICCountryCode
Indicates that an entity is associated with a specific country identified by its UIC (International Union of Railways) country code.
-
D.
countryCodeManaged
Indicates that an entity is responsible for administering or controlling the specified country code.
-
E.
callingCodeType
Indicates the type or category of a telephone calling code associated with an 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955ba250819085fa49e0059d06c1 |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc668ad3d881908a8a93a6a1d553e4 |
completed | April 1, 2026, 12:27 a.m. |
Created at: March 30, 2026, 7:11 p.m.