Triple
T32283007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DST Global |
E824749
|
entity |
| Predicate | checkSize |
P173924
|
FINISHED |
| Object | large late-stage rounds |
—
|
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: large late-stage rounds | Statement: [DST Global, checkSize, large late-stage rounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checkSize Context triple: [DST Global, checkSize, large late-stage rounds]
-
A.
hasSize
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
B.
hasSizeSystem
Indicates that an entity is associated with or defined according to a particular size measurement system.
-
C.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
D.
desiredSizeIndicates
Indicates that one entity specifies or reflects the preferred or intended size of another entity.
-
E.
sizeRestriction
Indicates that there is a limitation or constraint on the allowable size or dimensions of something in the relationship.
- F. None of above. chosen
Provenance (4 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bccc5be081908b121f4035b42dd9 |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:43 a.m.