Triple
T33114379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glen |
E847418
|
entity |
| Predicate | laterHasBody |
P131753
|
FINISHED |
| Object | human body |
—
|
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: human body | Statement: [Glen, laterHasBody, human body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterHasBody Context triple: [Glen, laterHasBody, human body]
-
A.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
B.
haveBody
chosen
Indicates that one entity possesses, contains, or is associated with another entity as its body or main physical/content component.
-
C.
hasLocalBody
Indicates that an entity is governed, administered, or represented by a specific local governing body or authority.
-
D.
hasInternalBody
Indicates that one entity possesses an internal body or internal bodily structure relative to another entity or context.
-
E.
hasSupportBody
Indicates that one entity serves as a supporting structure or body for another 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: May 1, 2026, 1:27 a.m.