Triple
T14023625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croesus |
E337397
|
entity |
| Predicate | proverbialExpression |
P78530
|
FINISHED |
| Object | “rich as Croesus” |
—
|
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: “rich as Croesus” | Statement: [Croesus, proverbialExpression, “rich as Croesus”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proverbialExpression Context triple: [Croesus, proverbialExpression, “rich as Croesus”]
-
A.
relatedProverb
chosen
Indicates that one entity is a proverb that is thematically or conceptually related to another entity.
-
B.
meaningOfPhrase
Indicates that one entity expresses or defines the semantic content or interpretation of a given phrase.
-
C.
expresses
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
-
D.
symbolicPhrase
Indicates a relationship where one entity is represented or expressed by a symbolic phrase associated with another entity.
-
E.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3d87b88190b038d334f4965369 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.