Triple
T1975693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professional Securities Market |
E42905
|
entity |
| Predicate | allowsListingOf |
P273
|
FINISHED |
| Object | bonds |
—
|
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: bonds | Statement: [Professional Securities Market, allowsListingOf, bonds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsListingOf Context triple: [Professional Securities Market, allowsListingOf, bonds]
-
A.
hasListingAuthority
Indicates that an entity has the official power or permission to create, approve, or manage listings for another entity or resource.
-
B.
listedWith
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
C.
isListedBy
Indicates that one entity appears as an item or entry in a list, catalog, or register maintained or provided by another entity.
-
D.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
E.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f835108190b0709ccf3a487a96 |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff9a09c8190a81fa13f4b85bc79 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.