Triple
T3886049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 944 Hidalgo |
E92942
|
entity |
| Predicate | hasObservationArc |
P51295
|
FINISHED |
| Object | over 100 years |
—
|
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: over 100 years | Statement: [944 Hidalgo, hasObservationArc, over 100 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObservationArc Context triple: [944 Hidalgo, hasObservationArc, over 100 years]
-
A.
hasObservation
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
-
B.
observationArc
chosen
Indicates a relationship where one entity serves as an observational link or span over which another entity is monitored, tracked, or measured across a period or range.
-
C.
hasObservationWavelength
Indicates the specific wavelength at which an observation or measurement is made or recorded.
-
D.
hasObservationFacility
Indicates that an entity possesses or is associated with a facility used for observing, monitoring, or collecting data about something.
-
E.
hasBeenObservedByOccultation
Indicates that an object or phenomenon has been detected or studied through an occultation event, where it is temporarily obscured by another body.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec942bfc8190a398fe370715a28b |
completed | March 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.