Triple
T30890434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Six Swans |
E786882
|
entity |
| Predicate | taleTypeName |
P170274
|
FINISHED |
| Object | The Six Swans |
—
|
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: The Six Swans | Statement: [The Six Swans, taleTypeName, The Six Swans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taleTypeName Context triple: [The Six Swans, taleTypeName, The Six Swans]
-
A.
namesakeType
Indicates the specific kind or category of namesake relationship that exists between two entities (for example, one being named after the other as a person, place, event, or object).
-
B.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
C.
تصنيف النوع
Indicates the classification relationship that assigns an entity to a particular type or category.
-
D.
eraNameType
Indicates the type or classification of a named historical or chronological era associated with an entity.
-
E.
tagType
Indicates the classification or category assigned to a tag, specifying what kind of tag it is or how it should be interpreted.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69208e9cc8190a88edc0d9cf1449d |
completed | May 3, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68c517f308190873c1c7e05a0c6d0 |
completed | May 2, 2026, 11:44 p.m. |
Created at: April 29, 2026, 8:49 p.m.