Triple
T38479569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSLV-C6 |
E915633
|
entity |
| Predicate | secondaryPayloadUserCommunity |
P201256
|
FINISHED |
| Object | amateur radio operators |
—
|
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: amateur radio operators | Statement: [PSLV-C6, secondaryPayloadUserCommunity, amateur radio operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryPayloadUserCommunity Context triple: [PSLV-C6, secondaryPayloadUserCommunity, amateur radio operators]
-
A.
scriptUserCommunity
Indicates a relationship where a user participates in, belongs to, or is associated with a particular community within a script or scripted system.
-
B.
communityAspect
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
C.
coreCommunity
Indicates that an entity belongs to the central or most essential group within a larger community.
-
D.
notableUserCommunity
Indicates that a user has a significant or distinguished presence, role, or recognition within a particular community.
-
E.
usedByCommunity
Indicates that something is utilized or adopted collectively by a particular community.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
| PDg | Predicate description generation | batch_69ffe12d61e0819098692270ab2625e3 |
completed | May 10, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:31 p.m.