Triple
T29595742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | guardians of the Golden Fleece |
E754289
|
entity |
| Predicate | guardedObjectType |
P167984
|
FINISHED |
| Object | magical ram’s fleece |
—
|
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: magical ram’s fleece | Statement: [guardians of the Golden Fleece, guardedObjectType, magical ram’s fleece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedObjectType Context triple: [guardians of the Golden Fleece, guardedObjectType, magical ram’s fleece]
-
A.
guardedStructure
Indicates that a structure is being protected or watched over by a guarding entity or mechanism.
-
B.
guardType
Indicates the specific kind or category of guarding role or protection associated with an entity.
-
C.
typicalObjectType
Indicates that something is a common or characteristic type of object typically associated with or involved in another entity or situation.
-
D.
guardedAs
Indicates that one entity is protected, watched over, or kept secure in the role or capacity specified by another entity.
-
E.
invariantType
Indicates that one entity has a type or classification that remains constant or unchanged under specified conditions or transformations.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 6:17 p.m.