Triple
T8926279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lex talionis |
E212545
|
entity |
| Predicate | hasCoreFormula |
P65390
|
FINISHED |
| Object | an eye for an eye |
—
|
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: an eye for an eye | Statement: [lex talionis, hasCoreFormula, an eye for an eye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreFormula Context triple: [lex talionis, hasCoreFormula, an eye for an eye]
-
A.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
B.
hasCoreExpression
chosen
Indicates that one entity serves as the fundamental or primary expression or representation of another entity.
-
C.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
D.
hasCoreTheory
Indicates that an entity is associated with, based on, or governed by a central underlying theory that defines its fundamental principles or framework.
-
E.
hasCoreFunction
Indicates that one entity serves as a primary or essential function or role of another entity.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66700fb48190874563e535f20437 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.