Triple
T36484481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian SMEs |
E898900
|
entity |
| Predicate | typicalSizeCategory |
P62521
|
FINISHED |
| Object | small enterprise |
—
|
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: small enterprise | Statement: [Canadian SMEs, typicalSizeCategory, small enterprise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSizeCategory Context triple: [Canadian SMEs, typicalSizeCategory, small enterprise]
-
A.
sizeCategory
chosen
Indicates the relative size classification assigned to an entity compared to others (e.g., small, medium, large).
-
B.
typicalFit
Indicates that one entity is a usual, expected, or characteristic match or correspondence for another in a given context.
-
C.
typicalCastSize
Indicates the usual or standard number of cast members involved in a production or performance.
-
D.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
E.
sizeStatus
Indicates the relative size condition or classification of one entity in relation to another or to a defined standard.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.