Triple
T23316509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AL-03 |
E590720
|
entity |
| Predicate | usesCodePrefix |
P133811
|
FINISHED |
| Object | AL |
—
|
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: AL | Statement: [AL-03, usesCodePrefix, AL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCodePrefix Context triple: [AL-03, usesCodePrefix, AL]
-
A.
tailCodePrefix
Indicates that one entity’s tail code begins with, or is prefixed by, the string represented by the other entity.
-
B.
usesCodeName
Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
-
C.
languageOfCodePrefix
Indicates that one entity is the programming language associated with, or identified by, the code prefix represented by the other entity.
-
D.
topLevelCodePrefix
chosen
Indicates that one code serves as a primary or highest-level prefix from which another, more specific code is derived or categorized.
-
E.
usesCodeSpace
Indicates that one entity employs or operates within a particular code space or coding environment provided by 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197816024819086c547ba89f84286 |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:06 p.m.