Triple
T28027071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAT12 |
E708152
|
entity |
| Predicate | supportsDataRegion |
P202097
|
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: [FAT12, supportsDataRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDataRegion Context triple: [FAT12, supportsDataRegion, true]
-
A.
supportsRegion
Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative region.
-
B.
supportsDataFrom
Indicates that one entity provides, validates, or underpins the data used or referenced by another entity.
-
C.
supportsRegionSelection
Indicates that an entity provides functionality for selecting a specific region or area within its scope.
-
D.
supportsDataBinding
Indicates that one entity enables or is compatible with automatic synchronization of data values between sources and targets (data binding) in another entity.
-
E.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
| PDg | Predicate description generation | batch_6a0051234cc08190adae6e2cfae2f8cc |
completed | May 10, 2026, 9:34 a.m. |
Created at: April 27, 2026, 8:13 p.m.