Triple
T15391572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electra paradox |
E368056
|
entity |
| Predicate | concernsRelation |
P84787
|
FINISHED |
| Object | “is identical with” |
—
|
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: “is identical with” | Statement: [Electra paradox, concernsRelation, “is identical with”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsRelation Context triple: [Electra paradox, concernsRelation, “is identical with”]
-
A.
subjectRelation
chosen
Indicates that one entity stands in a specified relational role or connection to another entity.
-
B.
concernsEntity
Indicates that something (such as an action, issue, or piece of information) is about or relevant to a particular entity.
-
C.
concernedSee
Indicates that one entity looks at or observes another with a sense of worry, care, or concern.
-
D.
concernsSet
Indicates that something is about, relates to, or involves a particular set as its primary subject or focus.
-
E.
concernsClause
Indicates that one entity (such as a document, statement, or discussion) is about, relates to, or addresses a particular clause.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7727a081908eff45bbc1633c8a |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.