Triple
T31995444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the White Swan |
E816980
|
entity |
| Predicate | hasFamousVariation |
P30580
|
FINISHED |
| Object | White Swan variation |
—
|
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: White Swan variation | Statement: [the White Swan, hasFamousVariation, White Swan variation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamousVariation Context triple: [the White Swan, hasFamousVariation, White Swan variation]
-
A.
famousVariant
chosen
Indicates that one entity is a well-known or widely recognized version or form of another entity.
-
B.
notableVariation
Indicates that one entity represents a significant or noteworthy deviation or difference from another entity within a given context.
-
C.
hasFamousVersionLabel
Indicates that an entity has an associated label describing a well-known or notable version of it.
-
D.
hasCelebrityVersion
Indicates that an entity has a special or adapted version associated with a celebrity.
-
E.
hasFamousPass
Indicates that an entity possesses or is associated with a well-known or historically significant pass (such as a route, corridor, or access point).
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 12:13 a.m.