Triple
T37794887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Body Love |
E942173
|
entity |
| Predicate | hasApproximateSideLength |
P18961
|
FINISHED |
| Object | LP-length |
—
|
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: LP-length | Statement: [Body Love, hasApproximateSideLength, LP-length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateSideLength Context triple: [Body Love, hasApproximateSideLength, LP-length]
-
A.
approximateSideLengthOrderOfMagnitude
Indicates that one entity’s side length is approximately the same order of magnitude as another entity’s side length, differing by no more than about a factor of ten.
-
B.
hasApproximateShape
Indicates that one entity has a shape that is similar to, but not exactly the same as, the shape of another entity.
-
C.
hasDimensionsApprox
chosen
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
-
D.
hasApproximateLengthCategory
Indicates that one entity is classified into a broad or approximate category based on its length.
-
E.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
- 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_69f76ee6f1f4819091e2cf9c9e6aee19 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 3, 2026, 4:19 p.m.