Triple
T23740670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Mann |
E586662
|
entity |
| Predicate | planetSurveyed |
P153516
|
FINISHED |
| Object | frozen ammonia-ice world in another galaxy |
—
|
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: frozen ammonia-ice world in another galaxy | Statement: [Dr. Mann, planetSurveyed, frozen ammonia-ice world in another galaxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetSurveyed Context triple: [Dr. Mann, planetSurveyed, frozen ammonia-ice world in another galaxy]
-
A.
surveyFunction
Indicates that an entity serves as a survey-related function or role in relation to another entity or context.
-
B.
surveyField
Indicates that an entity conducts, performs, or is responsible for surveying a particular field or area.
-
C.
surveyedIn
Indicates that an entity was included as part of the scope or coverage of a particular survey or data-collection effort.
-
D.
surveyBand
Indicates that an entity conducts or is associated with a survey using a specific observational band or frequency range.
-
E.
surveyMode
Indicates the method or format by which a survey is administered or conducted (e.g., online, phone, in-person).
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad61d908190a0a8493bbba95d49 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:11 p.m.