Triple
T13644783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andy’s backyard |
E326073
|
entity |
| Predicate | scaleRelativeToToys |
P23282
|
FINISHED |
| Object | appears vast and adventurous |
—
|
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: appears vast and adventurous | Statement: [Andy’s backyard, scaleRelativeToToys, appears vast and adventurous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaleRelativeToToys Context triple: [Andy’s backyard, scaleRelativeToToys, appears vast and adventurous]
-
A.
scaleComparison
chosen
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
-
B.
associatedScale
Indicates that one entity is linked or connected to a particular scale used to measure, classify, or evaluate it.
-
C.
areaScale
Indicates a proportional relationship where one area value is a scaled (enlarged or reduced) version of another by a specific factor.
-
D.
relativeSizeOnTethys
Indicates how the size of one entity compares to another specifically in the context of Tethys.
-
E.
setSize
Indicates assigning or changing the size or dimensions of an entity.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.