Triple
T1804927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Rice Genebank |
E40198
|
entity |
| Predicate | dataManagedIn |
P14669
|
FINISHED |
| Object | genebank information system |
—
|
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: genebank information system | Statement: [International Rice Genebank, dataManagedIn, genebank information system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataManagedIn Context triple: [International Rice Genebank, dataManagedIn, genebank information system]
-
A.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of 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.
managingCenter
Indicates that one entity serves as the administrative or coordinating center responsible for managing another entity or activity.
-
D.
dataControl
Indicates that one entity has the authority or capability to determine how another entity’s data is collected, used, shared, or managed.
-
E.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
- 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_69a88643a3388190a612f2ebe1fb29e7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba67721788190951beae25e885457 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61d514c081908197ac1f7c7d7a88 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.