Triple
T31021830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stock Exchange Automated Quotations |
E790468
|
entity |
| Predicate | informationUsers |
P7412
|
FINISHED |
| Object | brokers |
—
|
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: brokers | Statement: [Stock Exchange Automated Quotations, informationUsers, brokers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationUsers Context triple: [Stock Exchange Automated Quotations, informationUsers, brokers]
-
A.
dataUsers
chosen
Indicates a relationship where certain entities use, access, or consume specific data.
-
B.
otherUsers
Indicates a relationship where one or more users are distinguished as being different from a given primary or reference user.
-
C.
userBase
Indicates that one entity serves as the primary or foundational group of users associated with another entity.
-
D.
typeOfInformation
Indicates that one entity specifies the category or kind of information that characterizes or describes another entity.
-
E.
usesInformationFor
Indicates that one entity applies or exploits information obtained from another entity for a particular purpose or activity.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:58 p.m.