Triple
T24183670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QUIJOTE experiment |
E599490
|
entity |
| Predicate | observingStrategy |
P155605
|
FINISHED |
| Object | large-area sky 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: large-area sky survey | Statement: [QUIJOTE experiment, observingStrategy, large-area sky survey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observingStrategy Context triple: [QUIJOTE experiment, observingStrategy, large-area sky survey]
-
A.
observingTechnique
Indicates the method or procedure used to carry out an observation.
-
B.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
C.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of another entity.
-
D.
observationalStatus
Indicates the current state or condition of an observation, such as whether it has been made, recorded, verified, or remains pending.
-
E.
observedWith
Indicates that two or more entities are seen, detected, or recorded together in the same context, event, or observation.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 17, 2026, 11:34 p.m.