Triple
T33431108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PH-LAN |
E856132
|
entity |
| Predicate | codeFormatType |
P130
|
FINISHED |
| Object | alphanumeric |
—
|
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: alphanumeric | Statement: [PH-LAN, codeFormatType, alphanumeric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeFormatType Context triple: [PH-LAN, codeFormatType, alphanumeric]
-
A.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
B.
configFileFormat
Indicates the file format or syntax standard used by a configuration file.
-
C.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
-
D.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
E.
syntaxStyle
Indicates the stylistic or structural conventions used in the form or arrangement of an expression, statement, or code.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e48010788190bd60e56b378f4b4a |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.