Triple
T27613326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UserInfo Endpoint |
E700376
|
entity |
| Predicate | describedByMetadataField |
P172115
|
FINISHED |
| Object | userinfo_endpoint |
—
|
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: userinfo_endpoint | Statement: [UserInfo Endpoint, describedByMetadataField, userinfo_endpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedByMetadataField Context triple: [UserInfo Endpoint, describedByMetadataField, userinfo_endpoint]
-
A.
describedByURL
Indicates that an entity is documented, explained, or otherwise described at the given URL.
-
B.
describedAt
Indicates that something is explained, characterized, or detailed in a particular source, context, or location.
-
C.
sourceDescribedBy
Indicates that a source is documented, characterized, or otherwise explained by a particular description or descriptive resource.
-
D.
describedFrom
Indicates that something is characterized, explained, or defined based on information, perspective, or features originating from a particular source or reference point.
-
E.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 27, 2026, 2:12 p.m.