Triple
T27613348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UserInfo Endpoint |
E700376
|
entity |
| Predicate | scopeControls |
P53029
|
FINISHED |
| Object | which claims are returned |
—
|
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: which claims are returned | Statement: [UserInfo Endpoint, scopeControls, which claims are returned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeControls Context triple: [UserInfo Endpoint, scopeControls, which claims are returned]
-
A.
scopeOfControl
Indicates the extent or range within which an entity has authority, influence, or control over another entity or set of entities.
-
B.
scopeOption
Indicates that one entity specifies or constrains the range, extent, or applicability (scope) of another entity as an available option or setting.
-
C.
rangeControlledBy
chosen
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
D.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
E.
scopeDetail
Indicates a more specific or refined characterization of the extent, boundaries, or coverage of something within a broader scope.
- 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.