Triple
T33995516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camelot of Africa |
E871662
|
entity |
| Predicate | evokesComparisonTo |
P278
|
FINISHED |
| Object | Camelot |
—
|
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: Camelot | Statement: [Camelot of Africa, evokesComparisonTo, Camelot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evokesComparisonTo Context triple: [Camelot of Africa, evokesComparisonTo, Camelot]
-
A.
comparisonUses
Indicates that one entity employs another entity as a basis or tool for making a comparison.
-
B.
isComparedTo
chosen
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
C.
notableComparison
Indicates that one entity is being compared to another in a way that is especially significant, remarkable, or worthy of note.
-
D.
sometimesComparedTo
Indicates that one entity is occasionally likened or contrasted to another, but not consistently or universally.
-
E.
comparisonAspect
Indicates that two or more entities are being compared specifically with respect to a particular shared attribute or dimension.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f703cad27c81908186b67f1dc869a5 |
completed | May 3, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69f70101ba1c819099380274e6df9a4d |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:50 a.m.