Triple
T35506034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASTRO-F |
E1026152
|
entity |
| Predicate | surveyResolution |
P183364
|
FINISHED |
| Object | higher angular resolution than IRAS |
—
|
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: higher angular resolution than IRAS | Statement: [ASTRO-F, surveyResolution, higher angular resolution than IRAS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveyResolution Context triple: [ASTRO-F, surveyResolution, higher angular resolution than IRAS]
-
A.
surveyDepth
Indicates the measured vertical distance from a reference surface (such as ground or water level) down to the point where the survey or observation is taken.
-
B.
surveyMode
Indicates the method or format by which a survey is administered or conducted (e.g., online, phone, in-person).
-
C.
surveyFunction
Indicates that an entity serves as a survey-related function or role in relation to another entity or context.
-
D.
surveyStatus
Indicates the current state or phase of a survey within its lifecycle (e.g., planned, active, completed, or closed).
-
E.
surveyCoverage
Indicates that one entity’s survey or data collection activity extends over, includes, or accounts for another entity or area.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.