Triple
T18772578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milky Way open cluster system |
E459051
|
entity |
| Predicate | containsYoungPopulations |
P132909
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Milky Way open cluster system, containsYoungPopulations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsYoungPopulations Context triple: [Milky Way open cluster system, containsYoungPopulations, yes]
-
A.
hasDependentPopulation
Indicates that an entity has a population of individuals who are economically or socially dependent on others for support.
-
B.
targetedPopulation
Indicates the group of individuals or entities that an action, intervention, or effect is specifically directed toward.
-
C.
hasNotablePopulation
Indicates that an entity is recognized for having a significant or noteworthy number of inhabitants or members.
-
D.
hasPopulationNote
Indicates that there is a special remark, qualifier, or explanatory note associated with the population value of an entity.
-
E.
hasFocusPopulation
Indicates that an entity is specifically directed toward, designed for, or primarily concerns a particular target population or group.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:52 a.m.