Triple
T15448704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boundless Informant |
E370091
|
entity |
| Predicate | supportsAggregationBy |
P68691
|
FINISHED |
| Object | geographic region |
—
|
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: geographic region | Statement: [Boundless Informant, supportsAggregationBy, geographic region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAggregationBy Context triple: [Boundless Informant, supportsAggregationBy, geographic region]
-
A.
aggregationProperty
chosen
Indicates that one entity serves as an aggregation or summary of values or instances associated with another entity.
-
B.
supportsOperationsWith
Indicates that one entity enables, facilitates, or is compatible with the execution of operations involving another entity.
-
C.
supportsOperationsIn
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
-
D.
supportsPredicateFiltering
Indicates that the subject allows or enables filtering operations to be performed based on specific predicates or conditions.
-
E.
dataAggregation
Indicates the process by which multiple data points or datasets are combined into a summarized or consolidated form.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef9334c81908541e231b43eb012 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.