Triple
T29245528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sami Square |
E741429
|
entity |
| Predicate | hasSignificanceInBodyOfWorkOf |
P59323
|
FINISHED |
| Object | Vikram |
—
|
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: Vikram | Statement: [Sami Square, hasSignificanceInBodyOfWorkOf, Vikram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificanceInBodyOfWorkOf Context triple: [Sami Square, hasSignificanceInBodyOfWorkOf, Vikram]
-
A.
hasAuthorOfKeyWork
Indicates that an entity serves as the author or creator of a significant or primary work associated with another entity.
-
B.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
C.
hasAuthorOfSameWorkAs
Indicates that two authors are related by having written or contributed to the same work.
-
D.
workOfAuthorOf
Indicates that one entity is a work (such as a book, article, or artwork) created by the author associated with another entity.
-
E.
attestedInWorksOf
chosen
Indicates that something (such as a claim, form, or usage) is documented or evidenced within the works produced by a particular author or creator.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 28, 2026, 12:32 p.m.