Triple
T4164598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T12 |
E84414
|
entity |
| Predicate | followsFormat |
P35006
|
FINISHED |
| Object | Routing key plus unique identifier |
—
|
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: Routing key plus unique identifier | Statement: [T12, followsFormat, Routing key plus unique identifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsFormat Context triple: [T12, followsFormat, Routing key plus unique identifier]
-
A.
meetsFormat
chosen
Indicates that something conforms to, satisfies, or is compliant with a specified format or structural standard.
-
B.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
-
C.
hasMatchFormat
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
-
D.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
E.
includeFormat
Indicates that one entity contains or specifies the format or representation type of 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.