Triple
T4618161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heliades |
E100916
|
entity |
| Predicate | tearsBecame |
P6579
|
FINISHED |
| Object | amber |
—
|
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: amber | Statement: [Heliades, tearsBecame, amber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tearsBecame Context triple: [Heliades, tearsBecame, amber]
-
A.
beforeBecoming
Indicates that one state, role, or condition existed or occurred prior to another state, role, or condition coming into effect.
-
B.
became
chosen
Indicates a change of state or status in which one entity transitions into or assumes the role, condition, or identity of another.
-
C.
brokenUp
Indicates that a previously existing romantic or close relationship between two entities has ended.
-
D.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface of another entity.
-
E.
turnedToStone
Indicates that an entity has been transformed into stone, typically as a result of some magical or supernatural effect.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e247448190ad92f194cb1127c5 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.