Triple
T23244277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hipparcos Catalogue |
E581539
|
entity |
| Predicate | containsDataFor |
P86949
|
FINISHED |
| Object | over 100000 stars |
—
|
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 100000 stars | Statement: [Hipparcos Catalogue, containsDataFor, over 100000 stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDataFor Context triple: [Hipparcos Catalogue, containsDataFor, over 100000 stars]
-
A.
containsDataAbout
chosen
Indicates that one entity holds or includes information or records pertaining to another entity.
-
B.
hasSourceOfData
Indicates that one entity serves as the origin or provider of the data used or referenced by another entity.
-
C.
containsRecord
Indicates that one entity holds, includes, or stores a particular record within it.
-
D.
supportsDataFrom
Indicates that one entity provides, validates, or underpins the data used or referenced by another entity.
-
E.
collectsDataFor
Indicates that one entity gathers or records data on behalf of, or for the benefit of, another entity.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193ee37c8819091f799506fa532da |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.