Triple
T29843339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ram Chrysomallos |
E757859
|
entity |
| Predicate | fleeceBecame |
P167659
|
FINISHED |
| Object | Golden Fleece |
—
|
NE NERFINISHED |
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: Golden Fleece | Statement: [Ram Chrysomallos, fleeceBecame, Golden Fleece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleeceBecame Context triple: [Ram Chrysomallos, fleeceBecame, Golden Fleece]
-
A.
fledAfter
Indicates that one entity escaped or ran away after a particular event, action, or condition involving another entity occurred.
-
B.
fledDuring
Indicates that one entity escaped or ran away during the time period or event represented by the other entity.
-
C.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface of another entity.
-
D.
fledFrom
Indicates that one entity escaped or ran away from another entity or location.
-
E.
someFledTo
Indicates that at least one member of a group escaped or ran away from one place and went to another place.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6760b3d6081909d0e3748483989a4 |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66bd123108190b451eb6e23842adb |
completed | May 2, 2026, 9:25 p.m. |
Created at: April 29, 2026, 5:40 p.m.