Triple
T34916359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FireDAC |
E1007010
|
entity |
| Predicate | supportedIDE |
P48616
|
FINISHED |
| Object | RAD Studio |
E307739
|
NE 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: RAD Studio | Statement: [FireDAC, supportedIDE, RAD Studio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedIDE Context triple: [FireDAC, supportedIDE, RAD Studio]
-
A.
supportsIDEIntegration
Indicates that one entity provides compatibility or features that allow it to work seamlessly within or alongside an Integrated Development Environment (IDE).
-
B.
usedInIDE
Indicates that something (such as a tool, feature, or component) is utilized within an integrated development environment (IDE) as part of its functionality or workflow.
-
C.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
D.
supportedIn
chosen
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
E.
previousIDEName
Indicates that an entity previously had a different IDE name before its current one.
- F. None of above.
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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a8b149448190a521b4972018146b |
completed | June 21, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.