Triple
T11317119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arecibo L-band Feed Array survey |
E267994
|
entity |
| Predicate | hasSurveyType |
P35456
|
FINISHED |
| Object | wide-area survey |
—
|
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: wide-area survey | Statement: [Arecibo L-band Feed Array survey, hasSurveyType, wide-area survey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurveyType Context triple: [Arecibo L-band Feed Array survey, hasSurveyType, wide-area survey]
-
A.
surveyType
chosen
Indicates the specific category or kind of survey associated with an entity or activity.
-
B.
questionnaireType
Indicates the specific category or kind of questionnaire associated with an entity or interaction.
-
C.
surveySystemType
Indicates the type or category of system used to conduct or manage a survey.
-
D.
usesSurveyPoint
Indicates that an entity relies on or references a specific survey point as a positional or measurement basis in its activity or relationship.
-
E.
surveyedFor
Indicates that one entity has been examined, questioned, or assessed in order to gather information specifically about another entity or topic.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c3cf748190987838029d9f7fff |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.