Triple
T5406987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andromeda XV |
E120915
|
entity |
| Predicate | survey |
P31313
|
FINISHED |
| Object | CFHT MegaCam survey of M31 surroundings |
—
|
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: CFHT MegaCam survey of M31 surroundings | Statement: [Andromeda XV, survey, CFHT MegaCam survey of M31 surroundings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survey Context triple: [Andromeda XV, survey, CFHT MegaCam survey of M31 surroundings]
-
A.
surveyMode
Indicates the method or format by which a survey is administered or conducted (e.g., online, phone, in-person).
-
B.
surveyType
Indicates the specific category or kind of survey associated with an entity or activity.
-
C.
surveyBand
Indicates that an entity conducts or is associated with a survey using a specific observational band or frequency range.
-
D.
surveyMethod
Indicates the technique or procedure used to conduct a survey or collect survey data.
-
E.
surveys
chosen
Indicates that one entity systematically examines, questions, or assesses another entity or a situation to gather information or evaluate its state.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8793ab3c81909992b257d462a554 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.