Triple
T36337147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fremont Troll |
E894817
|
entity |
| Predicate | hasBodyPosition |
P196263
|
FINISHED |
| Object | crouching under bridge |
—
|
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: crouching under bridge | Statement: [Fremont Troll, hasBodyPosition, crouching under bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyPosition Context triple: [Fremont Troll, hasBodyPosition, crouching under bridge]
-
A.
hasHeadPosition
Indicates the specific spatial position or orientation of an entity’s head relative to a reference frame or context.
-
B.
hasBodyName
Indicates that an entity has a specific name assigned to its physical body.
-
C.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
D.
hasBodyTypeRelativeToAtlas
Indicates that an entity’s body type is characterized or classified in relation to a reference atlas or standard body-type model.
-
E.
hasTopBody
Indicates that one entity possesses or is characterized by a primary upper body section.
- F. None of above. chosen
Provenance (4 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fe189f2ea48190b8c4718f1353970e |
completed | May 8, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4:09 p.m.