Triple
T17006940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eircode system |
E412595
|
entity |
| Predicate | routingKeyLength |
P33158
|
FINISHED |
| Object | 3 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: 3 characters | Statement: [Eircode system, routingKeyLength, 3 characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routingKeyLength Context triple: [Eircode system, routingKeyLength, 3 characters]
-
A.
supportsKeyLength
Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
-
B.
identifierLength
chosen
Indicates the length or number of characters in an entity’s identifier.
-
C.
extensionLength
Indicates the length or magnitude of an extension from a reference point or base object.
-
D.
basePathLength
Indicates the length of the primary or reference path used as a baseline in a given context.
-
E.
supportsVariableKeyLength
Indicates that an entity is capable of operating correctly with cryptographic keys of varying lengths rather than a single fixed key size.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d3841e48819086dbc383cb4b1c16 |
completed | April 18, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.