Triple
T13822027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerald Network |
E332159
|
entity |
| Predicate | dataManagedAs |
P98727
|
FINISHED |
| Object | georeferenced site database |
—
|
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: georeferenced site database | Statement: [Emerald Network, dataManagedAs, georeferenced site database]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataManagedAs Context triple: [Emerald Network, dataManagedAs, georeferenced site database]
-
A.
dataManagement
Indicates the relationship in which an entity organizes, stores, maintains, and governs data throughout its lifecycle.
-
B.
isManagedThrough
chosen
Indicates that one entity is administered, controlled, or operated by means of another entity, typically specifying the mechanism, channel, or system used for its management.
-
C.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
D.
isManaged
Indicates that one entity exercises supervisory or administrative control over another entity.
-
E.
dataMaintained
Indicates that one entity is responsible for preserving, storing, or keeping another entity’s data up to date and accessible over time.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0284428081908043c55caeefb833 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.