Triple
T8611645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scratch API |
E203925
|
entity |
| Predicate | exposesEndpointType |
P57698
|
FINISHED |
| Object | REST-like HTTP endpoints |
—
|
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: REST-like HTTP endpoints | Statement: [Scratch API, exposesEndpointType, REST-like HTTP endpoints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposesEndpointType Context triple: [Scratch API, exposesEndpointType, REST-like HTTP endpoints]
-
A.
hasEndpointType
chosen
Indicates that an entity has a specific type or classification assigned to one of its endpoints.
-
B.
exposesTo
Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
-
C.
exposedAs
Indicates that one entity reveals or publicly identifies another entity as having a hidden, false, or previously concealed role, identity, or nature.
-
D.
exposureType
Indicates the specific manner or context in which one entity is exposed to another entity, condition, or influence.
-
E.
exportsType
Indicates that one entity sends or sells a particular type or category of goods, services, or resources to another entity across a boundary (such as international borders).
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46fc31e08190aab5ab8f92f3315c |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.