Triple
T4617700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Cluster |
E100905
|
entity |
| Predicate | isPopularTargetFor |
P729
|
FINISHED |
| Object | amateur astronomers |
—
|
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 astronomers | Statement: [Double Cluster, isPopularTargetFor, amateur astronomers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularTargetFor Context triple: [Double Cluster, isPopularTargetFor, amateur astronomers]
-
A.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
B.
isPopularWith
chosen
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
-
C.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
D.
isPopularOnSocialMedia
Indicates that an entity is widely followed, frequently engaged with, or broadly recognized across social media platforms.
-
E.
isStandardizationTargetOf
Indicates that an entity is the object or subject being standardized within a standardization process, activity, or initiative.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.