Triple
T7933216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloud Functions for Firebase |
E184230
|
entity |
| Predicate | supportsTriggerType |
P36418
|
FINISHED |
| Object | HTTP request |
—
|
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: HTTP request | Statement: [Cloud Functions for Firebase, supportsTriggerType, HTTP request]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTriggerType Context triple: [Cloud Functions for Firebase, supportsTriggerType, HTTP request]
-
A.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
B.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
C.
supportedEvent
chosen
Indicates that an entity is capable of recognizing, handling, or being associated with a particular type of event.
-
D.
supportsProgramType
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
-
E.
supportsPatternType
Indicates that one entity is compatible with, or capable of handling, a specified pattern type.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3acfd2a88190b1a13cd6fdedc272 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.