Triple
T9592175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scripps Institution of Oceanography pier |
E231446
|
entity |
| Predicate | dataFromPierUsedBy |
P7412
|
FINISHED |
| Object | scientists |
—
|
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: scientists | Statement: [Scripps Institution of Oceanography pier, dataFromPierUsedBy, scientists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataFromPierUsedBy Context triple: [Scripps Institution of Oceanography pier, dataFromPierUsedBy, scientists]
-
A.
reportsUsedBy
Indicates that a report is utilized or referenced by another entity (such as a user, system, or process).
-
B.
dataPortal
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.
dataUsers
chosen
Indicates a relationship where certain entities use, access, or consume specific data.
-
D.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
E.
platformUsage
Indicates how an entity uses, engages with, or relies on a particular platform for its activities or services.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a11ec7081908dc580de2f369706 |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.