Triple
T8510774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delphic maxim "know thyself" |
E201446
|
entity |
| Predicate | hasCommonEnglishForm |
P3437
|
FINISHED |
| Object | "know thyself" |
—
|
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: "know thyself" | Statement: [Delphic maxim "know thyself", hasCommonEnglishForm, "know thyself"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonEnglishForm Context triple: [Delphic maxim "know thyself", hasCommonEnglishForm, "know thyself"]
-
A.
hasEnglishName
chosen
Indicates that an entity is associated with a name expressed in the English language.
-
B.
hasTwoWordForm
Indicates that an entity is represented or expressed using a form consisting of exactly two words.
-
C.
hasStandardizedNameInEnglish
Indicates that an entity is associated with a specific standardized or officially recognized name expressed in English.
-
D.
hasCommonLoanwordsFrom
Indicates that two languages share loanwords that originate from the same source language.
-
E.
hasThreeLetterForm
Indicates that an entity’s written or symbolic form consists of exactly three letters.
- 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe608e5b08190a6d551793e8ed94b |
completed | March 31, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:15 p.m.