Triple
T29843346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ram Chrysomallos |
E757859
|
entity |
| Predicate | fleeceGuardedBy |
P1328
|
FINISHED |
| Object | dragon of Colchis |
—
|
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: dragon of Colchis | Statement: [Ram Chrysomallos, fleeceGuardedBy, dragon of Colchis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleeceGuardedBy Context triple: [Ram Chrysomallos, fleeceGuardedBy, dragon of Colchis]
-
A.
laterGuardedBy
Indicates that an entity is protected or guarded by another entity at a later time or in a subsequent state or phase.
-
B.
guardType
Indicates the specific kind or category of guarding role or protection associated with an entity.
-
C.
isProtectedBy
chosen
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
D.
guardFeature
Indicates that one entity protects, secures, or restricts access to a particular feature of another entity.
-
E.
heldToProtect
Indicates that one entity is kept in someone’s possession or custody for the purpose of safeguarding or protecting it.
- 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_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_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 5:40 p.m.