Triple
T23964652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Sharpen Iron |
E604031
|
entity |
| Predicate | titlePhraseDerivedFrom |
P12689
|
FINISHED |
| Object | biblical proverb "iron sharpeneth iron" |
—
|
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: biblical proverb "iron sharpeneth iron" | Statement: [Iron Sharpen Iron, titlePhraseDerivedFrom, biblical proverb "iron sharpeneth iron"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titlePhraseDerivedFrom Context triple: [Iron Sharpen Iron, titlePhraseDerivedFrom, biblical proverb "iron sharpeneth iron"]
-
A.
titleDerivedFrom
chosen
Indicates that the title of one entity is obtained or adapted from another entity.
-
B.
titlePhrase
Indicates that one entity is a phrase functioning as the title or name of another entity.
-
C.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
D.
titlePattern
Indicates that there is a specific structural or textual pattern that the title of an entity is expected to follow.
-
E.
titleBasis
Indicates that one entity serves as the basis or source material for the title or name 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1d7077881909d4774b7040cd722 |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:24 p.m.