Triple
T33720363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leuresthes |
E863993
|
entity |
| Predicate | spawningTrigger |
P177245
|
FINISHED |
| Object | high tides |
—
|
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: high tides | Statement: [Leuresthes, spawningTrigger, high tides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spawningTrigger Context triple: [Leuresthes, spawningTrigger, high tides]
-
A.
spawns
Indicates that one entity generates, creates, or gives rise to another entity, often as an origin or source.
-
B.
spawningLocation
Indicates the place or environment where an entity originates, appears, or is generated.
-
C.
trapTrigger
Indicates that an entity activates or sets off a trap in the environment.
-
D.
canSpawnWith
Indicates that one entity is able to appear, be created, or originate in conjunction with another entity under the same conditions or context.
-
E.
diesAfterSpawning
Indicates that an entity dies shortly after producing offspring or completing its spawning process.
- F. None of above. chosen
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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6faeac9288190ac7ce78ea3cdb622 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:44 a.m.