Triple
T23354455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tycho Catalogue |
E593005
|
entity |
| Predicate | accessFormat |
P130
|
FINISHED |
| Object | machine-readable catalog |
—
|
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: machine-readable catalog | Statement: [Tycho Catalogue, accessFormat, machine-readable catalog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessFormat Context triple: [Tycho Catalogue, accessFormat, machine-readable catalog]
-
A.
storageFormat
Indicates the specific way in which data or content is physically or logically organized, encoded, and stored.
-
B.
accessMode
Indicates the manner or method by which an entity can be accessed, used, or interacted with.
-
C.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
D.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
E.
accessProtocol
Indicates the method or rules by which one entity is allowed to access or communicate with another entity or resource.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a169bb88190a2ca659fce1133e5 |
completed | April 29, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:20 p.m.