Triple
T31003093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloudy Bay Pelorus |
E789991
|
entity |
| Predicate | bubbles |
P79934
|
FINISHED |
| Object | fine persistent bead |
—
|
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: fine persistent bead | Statement: [Cloudy Bay Pelorus, bubbles, fine persistent bead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bubbles Context triple: [Cloudy Bay Pelorus, bubbles, fine persistent bead]
-
A.
bubbleCharacteristic
Indicates that one entity has a specific property, feature, or quality that characterizes a bubble or bubble-like state in relation to another entity or context.
-
B.
bubbleState
chosen
Indicates the current status or condition of a bubble within a process, system, or environment (e.g., whether it exists, is active, stable, or has changed).
-
C.
blows
Indicates that one entity forcefully expels air or creates a current of air directed toward or acting upon another entity.
-
D.
budding
Indicates that one entity is forming or developing from another, typically as an initial or emerging stage of growth or creation.
-
E.
bubbleLocation
Indicates the spatial position or area where a bubble is situated or occurs.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:57 p.m.