Triple
T16494948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turritopsis dohrnii |
E400657
|
entity |
| Predicate | revertsFromStage |
P96178
|
FINISHED |
| Object | medusa |
—
|
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: medusa | Statement: [Turritopsis dohrnii, revertsFromStage, medusa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revertsFromStage Context triple: [Turritopsis dohrnii, revertsFromStage, medusa]
-
A.
returnToStage
Indicates that an entity goes back onto a stage or performance area after having left it.
-
B.
canRevertTo
chosen
Indicates that one state, version, or condition has the ability to be changed back or restored to another prior state, version, or condition.
-
C.
retrocededTo
Indicates that control, ownership, or rights over something were returned or transferred back from one entity to another.
-
D.
transitionStageBetween
Indicates a relationship where one state or phase serves as an intermediate or connecting stage between two other states or phases in a process or sequence.
-
E.
stagedBy
Indicates that an event, performance, or production is organized, directed, or put on by a particular agent or 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e3276b88190946a669b4d893a54 |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.