Triple
T20803792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FINRA CRD |
E512104
|
entity |
| Predicate | hasUserInterfaceFor |
P12981
|
FINISHED |
| Object | member firms |
—
|
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: member firms | Statement: [FINRA CRD, hasUserInterfaceFor, member firms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUserInterfaceFor Context triple: [FINRA CRD, hasUserInterfaceFor, member firms]
-
A.
hasCommandLineInterface
Indicates that an entity provides or supports interaction through a command-line interface (CLI).
-
B.
userInterface
Indicates a relationship where one entity serves as the interface or interaction layer through which a user engages with another system, service, or resource.
-
C.
supportsGraphicalUserInterface
Indicates that an entity is capable of operating with or providing a graphical user interface for interaction.
-
D.
hasInterface
chosen
Indicates that one entity provides, exposes, or is connected through a defined interface to another entity.
-
E.
supportsUserInteraction
Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2b2d5688190aaa58a2594d4787c |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:39 p.m.