Triple
T27664790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YouTube Data API |
E697201
|
entity |
| Predicate | accessEndpoint |
P6055
|
FINISHED |
| Object | https://www.googleapis.com/youtube/v3 |
—
|
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: https://www.googleapis.com/youtube/v3 | Statement: [YouTube Data API, accessEndpoint, https://www.googleapis.com/youtube/v3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessEndpoint Context triple: [YouTube Data API, accessEndpoint, https://www.googleapis.com/youtube/v3]
-
A.
accessURL
chosen
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
B.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
C.
accessPath
Indicates a path, route, or means by which something can be reached, entered, or accessed.
-
D.
typicalEndpoint
Indicates that something represents the standard or commonly used endpoint associated with another entity or process.
-
E.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 2:37 p.m.