Triple

T6745994
Position Surface form Disambiguated ID Type / Status
Subject Larissa E154214 entity
Predicate relativePositionInSystem P72711 FINISHED
Object inner regular satellite of Neptune 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: inner regular satellite of Neptune | Statement: [Larissa, relativePositionInSystem, inner regular satellite of Neptune]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relativePositionInSystem
Context triple: [Larissa, relativePositionInSystem, inner regular satellite of Neptune]
  • A. relativePosition
    Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
  • B. positionedRelativeTo
    Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
  • C. positionRelativeToBuilding
    Indicates the spatial relationship of an entity’s location with respect to a specific building (e.g., in front of, behind, adjacent to, on top of).
  • D. relativePositionOnCourse
    Indicates the positional relationship of one participant or object relative to another along a defined course or route.
  • E. relativeMotionType
    Indicates the type or nature of motion occurring between two entities relative to one another.
  • 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_69c6880ef37881909268a5a7299b9293 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d1b74ae081908575c4e47c0ef297 completed March 27, 2026, 6:51 p.m.
PD Predicate disambiguation batch_69c6d09067a0819087ed6c820f4699f8 completed March 27, 2026, 6:46 p.m.
PDg Predicate description generation batch_69c6d14e18d481908aaac34897c650f1 completed March 27, 2026, 6:49 p.m.
Created at: March 27, 2026, 2:10 p.m.