Triple
T35506384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPAC |
E1026160
|
entity |
| Predicate | dataServices |
P14669
|
FINISHED |
| Object | data archiving |
—
|
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: data archiving | Statement: [IPAC, dataServices, data archiving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataServices Context triple: [IPAC, dataServices, data archiving]
-
A.
dataAre
Indicates that one entity serves as the data or informational content associated with another entity.
-
B.
dataPortal
chosen
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
C.
data
Indicates that one entity serves as informational content, measurements, or recorded values associated with another entity.
-
D.
dataAvailableAs
Indicates that specific data can be accessed or obtained in a particular form, format, or representation.
-
E.
dataReturned
Indicates that some data has been sent back or provided as a result of a request, query, or operation.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.