Triple
T37720073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godot |
E939558
|
entity |
| Predicate | nameResembles |
P106359
|
FINISHED |
| Object | God |
—
|
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: God | Statement: [Godot, nameResembles, God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameResembles Context triple: [Godot, nameResembles, God]
-
A.
namedForSimilarityTo
chosen
Indicates that one entity is given its name because of a perceived resemblance or likeness to another entity.
-
B.
nameContrastsWith
Indicates that one name is deliberately chosen or used to highlight a difference or opposition in meaning, style, or identity relative to another name.
-
C.
nameLiterallyMeans
Indicates that the literal meaning or direct translation of one entity’s name is given by the other entity.
-
D.
namesakeDescription
Indicates that the object provides a descriptive explanation of why or how the subject is considered a namesake of something or someone.
-
E.
nameRepresents
Indicates that a given name stands for, denotes, or is used to identify a particular 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.