Triple
T36491425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flickr30k |
E899059
|
entity |
| Predicate | hasScaleComparedTo |
P23282
|
FINISHED |
| Object | larger than Flickr8k |
—
|
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: larger than Flickr8k | Statement: [Flickr30k, hasScaleComparedTo, larger than Flickr8k]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScaleComparedTo Context triple: [Flickr30k, hasScaleComparedTo, larger than Flickr8k]
-
A.
hasScale
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
-
B.
comparativeScale
Indicates a relationship where one entity is evaluated relative to another along a shared scale or dimension (such as size, intensity, or degree).
-
C.
scaleComparison
chosen
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
-
D.
hasScaleSize
Indicates that one entity possesses a scale characterized by a particular size or magnitude in relation to another entity or value.
-
E.
hasScales
Indicates that an entity possesses scales as a surface covering or body feature.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:10 p.m.