Triple
T25639003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megaclite |
E642783
|
entity |
| Predicate | satelliteGroupType |
P158945
|
FINISHED |
| Object | distant outer irregular group |
—
|
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: distant outer irregular group | Statement: [Megaclite, satelliteGroupType, distant outer irregular group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: satelliteGroupType Context triple: [Megaclite, satelliteGroupType, distant outer irregular group]
-
A.
satelliteType
Indicates that one entity is classified as a specific type or category of satellite relative to another entity.
-
B.
satelliteGroupCharacteristic
chosen
Indicates a characteristic or property that applies to a group of satellites considered collectively.
-
C.
satelliteBand
Indicates that something operates in, uses, or is associated with a specific frequency band within the satellite communication spectrum.
-
D.
typeOfSatelliteOperated
Indicates that one entity operates or manages a satellite of a specified type or category in relation to another entity.
-
E.
satelliteSystem
Indicates a relationship where one system functions as a satellite or subordinate system orbiting, supporting, or depending on another primary system.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa64332081909df65f8b4380f152 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 5:38 p.m.