Triple
T35005265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JEL classification system |
E1009791
|
entity |
| Predicate | hasCodeExample |
P30248
|
FINISHED |
| Object | A10 |
—
|
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: A10 | Statement: [JEL classification system, hasCodeExample, A10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodeExample Context triple: [JEL classification system, hasCodeExample, A10]
-
A.
hasInwardCodeExample
Indicates that an entity is associated with a specific example of an inward (local) postal code used to illustrate or clarify that code segment.
-
B.
hasExample
Indicates that one entity serves as an instance, illustration, or concrete example of another entity.
-
C.
codeExample
chosen
Indicates that one entity provides a snippet or sample of source code that illustrates how to use, implement, or demonstrate another entity.
-
D.
hasExampleImplementation
Indicates that an entity is accompanied by a concrete implementation that serves as an example of how it can be realized or used.
-
E.
hasExampleProvider
Indicates that one entity serves as an example provider or source of illustrative instances 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.