Triple
T29843345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ram Chrysomallos |
E757859
|
entity |
| Predicate | fleeceDedicatedTo |
P168193
|
FINISHED |
| Object | Ares |
—
|
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: Ares | Statement: [Ram Chrysomallos, fleeceDedicatedTo, Ares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleeceDedicatedTo Context triple: [Ram Chrysomallos, fleeceDedicatedTo, Ares]
-
A.
fleeceBecame
Indicates that something changed state to become fleece or took on fleece-like characteristics.
-
B.
dedicatedToBrand
Indicates that something (such as a resource, activity, or feature) is exclusively or primarily allocated or committed to a specific brand.
-
C.
fiberwiseDescription
Indicates a description or characterization that is given separately for each fiber in a fibered or parameterized structure, specifying how the relationship or action behaves over individual fibers.
-
D.
fur
Indicates that one entity has fur covering its body or surface.
-
E.
fleesWith
Indicates that one entity escapes or runs away together with another entity, sharing the act of fleeing as companions or partners.
- 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_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 5:40 p.m.