Triple
T27613327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UserInfo Endpoint |
E700376
|
entity |
| Predicate | metadataFieldDefinedIn |
P62335
|
FINISHED |
| Object | OpenID Provider Metadata |
—
|
NE NERFINISHED |
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: OpenID Provider Metadata | Statement: [UserInfo Endpoint, metadataFieldDefinedIn, OpenID Provider Metadata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metadataFieldDefinedIn Context triple: [UserInfo Endpoint, metadataFieldDefinedIn, OpenID Provider Metadata]
-
A.
definedInField
Indicates that something (such as a concept, method, or element) is formally specified, declared, or established within a particular field, domain, or area of study.
-
B.
metadataType
Indicates that one entity specifies the kind or category of metadata associated with another entity.
-
C.
metaProperty
Indicates that one property functions as a higher-level descriptor or attribute about another property, rather than about an entity directly.
-
D.
documentedField
Indicates that a particular field or attribute has been formally recorded or described in documentation.
-
E.
metadataLocation
chosen
Indicates the location or source where descriptive or administrative information about an entity is stored or can be accessed.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f630d5c31081909d20e8165cc0515f |
completed | May 2, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:12 p.m.