Triple
T8919107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eighth Wonder of the World |
E212365
|
entity |
| Predicate | impliesRankingAs |
P86403
|
FINISHED |
| Object | beyond the Seven Wonders of the World |
—
|
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: beyond the Seven Wonders of the World | Statement: [Eighth Wonder of the World, impliesRankingAs, beyond the Seven Wonders of the World]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesRankingAs Context triple: [Eighth Wonder of the World, impliesRankingAs, beyond the Seven Wonders of the World]
-
A.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
B.
usesRank
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
C.
associatedWithRank
Indicates a relationship where an entity is linked to a specific rank, level, or hierarchical position.
-
D.
representsRank
Indicates that one entity serves as the rank, status, or hierarchical level assigned to another entity.
-
E.
hasRankingFactor
Indicates that one entity contributes as a factor to determining the ranking or ordered position of another entity.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6613639881909090d060f388a865 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc600a59708190ae426044bbcd7929 |
completed | April 1, 2026, midnight |
Created at: March 30, 2026, 6:56 p.m.