Triple
T3732916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleeping Giant |
E79110
|
entity |
| Predicate | silhouetteResembles |
P40118
|
FINISHED |
| Object | reclining giant |
—
|
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: reclining giant | Statement: [Sleeping Giant, silhouetteResembles, reclining giant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: silhouetteResembles Context triple: [Sleeping Giant, silhouetteResembles, reclining giant]
-
A.
resembles
Indicates that one entity is similar in appearance, form, or characteristics to another.
-
B.
hasSilhouetteShape
chosen
Indicates that one entity has the overall outline or contour shape specified or characterized by another entity.
-
C.
materiallySimilarTo
Indicates that two entities share substantially the same physical or material characteristics, composition, or properties, though they may not be exactly identical.
-
D.
introducedSilhouette
Indicates that one entity caused another entity to first appear or be presented in outline or partial form, rather than in full detail.
-
E.
archaellaSimilarity
Indicates that two entities share a similarity or resemblance in their archaella (archaeal flagella) structures or characteristics.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb2277a48190ae7594c4c4965a01 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.