Triple
T33362253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green fluorescent protein |
E854252
|
entity |
| Predicate | originallyIsolatedFrom |
P202070
|
FINISHED |
| Object | Aequorea victoria |
E400658
|
NE 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: Aequorea victoria | Statement: [Green fluorescent protein, originallyIsolatedFrom, Aequorea victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyIsolatedFrom Context triple: [Green fluorescent protein, originallyIsolatedFrom, Aequorea victoria]
-
A.
firstIsolatedFrom
chosen
Indicates that the subject entity was the original source from which the object entity was first isolated or obtained.
-
B.
isolatedBy
Indicates that one entity has been separated or kept apart from another entity or set of entities, preventing interaction or influence between them.
-
C.
isolateFrom
Indicates that one entity is separated or kept apart from another entity or source.
-
D.
firstIsolationPlace
Indicates the location where an entity was initially placed into isolation for the first time.
-
E.
originallyIndependentOf
Indicates that one entity was initially separate from, and not derived from or influenced by, another entity at the outset.
- F. None of above.
Provenance (4 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a030f1480148190a5e8c8926ded252c |
completed | May 12, 2026, 11:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3576e29a7881909fab59ad73e26aaf |
completed | June 19, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a030e7f5fa481909696733defefcc20 |
completed | May 12, 2026, 11:26 a.m. |
Created at: May 1, 2026, 1:34 a.m.