Triple
T35005263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JEL classification system |
E1009791
|
entity |
| Predicate | hasTopLevelCodeFormat |
P133811
|
FINISHED |
| Object | single capital letter |
—
|
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: single capital letter | Statement: [JEL classification system, hasTopLevelCodeFormat, single capital letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopLevelCodeFormat Context triple: [JEL classification system, hasTopLevelCodeFormat, single capital letter]
-
A.
hasTopLevel
Indicates that one entity is the highest or primary element within a hierarchy or structure relative to another entity.
-
B.
topLevelCodePrefix
chosen
Indicates that one code serves as a primary or highest-level prefix from which another, more specific code is derived or categorized.
-
C.
hasUpperLevelFunction
Indicates that one function operates at a higher or more abstract level than another function within a hierarchical relationship.
-
D.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
E.
hasCodeElementsFor
Indicates a relationship where one entity contains, defines, or is associated with specific code elements (such as classes, methods, or functions) that implement or support 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_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:01 p.m.