Triple
T31576592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FishBase |
E805712
|
entity |
| Predicate | hasDataScope |
P158173
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [FishBase, hasDataScope, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataScope Context triple: [FishBase, hasDataScope, global]
-
A.
hasScope
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
B.
hasScopeRule
Indicates that a given entity is governed, constrained, or interpreted according to a particular scope-defining rule.
-
C.
hasAffiliationScope
Indicates the scope or extent within which an affiliation or association between entities is valid or applies.
-
D.
hasRepresentationScope
Indicates that something is represented, described, or modeled only within a specified scope, context, or domain.
-
E.
hasDataDomain
chosen
Indicates that something is associated with, constrained by, or operates within a particular data domain or scope of data.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 30, 2026, 10:22 p.m.