Triple
T27665140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azure REST APIs |
E697208
|
entity |
| Predicate | followsArchitectureStyle |
P179203
|
FINISHED |
| Object | REST |
—
|
NE NERFINISHED |
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: REST | Statement: [Azure REST APIs, followsArchitectureStyle, REST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsArchitectureStyle Context triple: [Azure REST APIs, followsArchitectureStyle, REST]
-
A.
architecturalStyle
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
B.
architecturalStyleIncludes
Indicates that a structure, building, or design incorporates or exemplifies a particular architectural style as one of its defining characteristics.
-
C.
architecturalStyleSimilarTo
Indicates that two entities share a comparable or closely related architectural style in form, design, or aesthetic characteristics.
-
D.
architecturalStyleCombines
Indicates that something incorporates elements or characteristics from multiple architectural styles into a single design.
-
E.
architecturalStylePromoted
Indicates the architectural style that an entity actively supported, advocated for, or helped popularize.
- F. None of above. chosen
Provenance (4 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 27, 2026, 2:37 p.m.