Triple
T26412655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tethys Trojan moons |
E664001
|
entity |
| Predicate | haveDynamicalType |
P17318
|
FINISHED |
| Object | Trojan moon |
—
|
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: Trojan moon | Statement: [Tethys Trojan moons, haveDynamicalType, Trojan moon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveDynamicalType Context triple: [Tethys Trojan moons, haveDynamicalType, Trojan moon]
-
A.
hasDynamicalClass
chosen
Indicates that an entity belongs to a specific category defined by its dynamical or motion-related behavior (e.g., orbital or kinematic characteristics).
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
isPartOfDynamically
Indicates that one entity is currently a component or member of another entity in a way that can change over time or at runtime.
-
D.
hasActingType
Indicates that an entity participates in or performs an action in a specified manner, role, or mode of acting.
-
E.
hasDynamics
Indicates that one entity exhibits or is characterized by specific dynamic behavior, changes, or variations over time in relation to another entity or context.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f611325fd48190898639883fb113fd |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:39 p.m.