Triple
T2798156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reg A |
E53087
|
entity |
| Predicate | targetIssuerType |
P10221
|
FINISHED |
| Object | smaller companies |
—
|
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: smaller companies | Statement: [Reg A, targetIssuerType, smaller companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetIssuerType Context triple: [Reg A, targetIssuerType, smaller companies]
-
A.
targetIssuerProfile
Indicates a relationship where a specific profile is designated as the primary or intended issuer in a given context.
-
B.
issuerType
chosen
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
C.
issuerOperatesIn
Indicates that an issuing entity conducts business activities or has operational presence within a specified geographic area or jurisdiction.
-
D.
assignedToIssuer
Indicates that a responsibility, task, or item has been allocated or designated to the issuer.
-
E.
issuerFounded
Indicates that one entity is the organization or person that established or created the other entity at its founding.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddf204148190a53f3f30d645d94c |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.