Triple
T23944626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post-it Notes |
E602880
|
entity |
| Predicate | hasStandardSize |
P12918
|
FINISHED |
| Object | 3 in x 3 in |
—
|
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: 3 in x 3 in | Statement: [Post-it Notes, hasStandardSize, 3 in x 3 in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardSize Context triple: [Post-it Notes, hasStandardSize, 3 in x 3 in]
-
A.
hasStandardizedDimensions
chosen
Indicates that an entity conforms to a predefined, uniform set of measurements or size specifications.
-
B.
hasSizeSystem
Indicates that an entity is associated with or defined according to a particular size measurement system.
-
C.
hasSize
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
D.
hasScaleSize
Indicates that one entity possesses a scale characterized by a particular size or magnitude in relation to another entity or value.
-
E.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02d07b08190acbcbb646cd9a58e |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:11 p.m.