Triple
T21738352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Phoenix |
E536584
|
entity |
| Predicate | targetSelectionCriterion |
P136
|
FINISHED |
| Object | Sun-like stars |
—
|
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: Sun-like stars | Statement: [Project Phoenix, targetSelectionCriterion, Sun-like stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetSelectionCriterion Context triple: [Project Phoenix, targetSelectionCriterion, Sun-like stars]
-
A.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
selectionCharacteristic
Indicates a distinguishing feature or criterion used to choose or differentiate one entity from others.
-
C.
selectedTo
Indicates that one entity has been chosen or designated from a set of candidates to perform a role, receive something, or participate in an activity in relation to another entity.
-
D.
targetCandidate
Indicates that an entity is being considered or designated as a potential target for selection, action, or further evaluation.
-
E.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd0e94c4819096bace0c661f5156 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.