Triple
T19703490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action API |
E473152
|
entity |
| Predicate | endpointPath |
P82537
|
FINISHED |
| Object | /w/api.php |
—
|
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: /w/api.php | Statement: [Action API, endpointPath, /w/api.php]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endpointPath Context triple: [Action API, endpointPath, /w/api.php]
-
A.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
B.
accessPath
chosen
Indicates a path, route, or means by which something can be reached, entered, or accessed.
-
C.
endpointFeature
Indicates that a particular feature, capability, or characteristic is associated with, provided by, or available at a specific endpoint.
-
D.
endPointExample
Indicates that something serves as a representative or illustrative instance of a particular endpoint.
-
E.
secondaryEndpoint
Indicates that something serves as an additional, non-primary endpoint or target associated with a main endpoint in a relationship or process.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b8707081908fbf96c989d2d52d |
completed | April 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.