Triple
T27662142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XML API |
E697148
|
entity |
| Predicate | supportsRegionSelection |
P200381
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [XML API, supportsRegionSelection, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRegionSelection Context triple: [XML API, supportsRegionSelection, true]
-
A.
supportsRegion
Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative region.
-
B.
supportsRegionRestriction
Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
-
C.
supportsRegionBiasing
Indicates that the subject is capable of applying or honoring region-specific preferences or priorities in its behavior or processing.
-
D.
homeRegionSupport
Indicates that an entity receives backing, endorsement, or favorable conditions from its own home region or local area.
-
E.
usesRegionType
Indicates that one entity operates within, is configured for, or otherwise makes use of a specified type of region.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
| PDg | Predicate description generation | batch_69ff878e8334819097e3c4bb5ca6ffa5 |
completed | May 9, 2026, 7:14 p.m. |
Created at: April 27, 2026, 2:37 p.m.