Triple
T35016937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon & Marcy |
E1010078
|
entity |
| Predicate | revealsRelationshipBetween |
P83409
|
FINISHED |
| Object | Simon Petrikov |
—
|
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: Simon Petrikov | Statement: [Simon & Marcy, revealsRelationshipBetween, Simon Petrikov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revealsRelationshipBetween Context triple: [Simon & Marcy, revealsRelationshipBetween, Simon Petrikov]
-
A.
showsRelationshipWith
chosen
Indicates that one entity visually or explicitly presents or demonstrates its connection or association with another entity.
-
B.
coversRelationship
Indicates that one entity extends over, includes, or provides encompassing coverage for another entity or set of entities.
-
C.
expressesRelationBetween
Indicates that one entity conveys, communicates, or articulates a specific relationship or connection between two or more entities.
-
D.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association with another entity.
-
E.
definesRelationshipBetween
Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.