Triple
T32082162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gheorghe (surname) |
E819327
|
entity |
| Predicate | equivalentGivenName |
P176360
|
FINISHED |
| Object | George |
—
|
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: George | Statement: [Gheorghe (surname), equivalentGivenName, George]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentGivenName Context triple: [Gheorghe (surname), equivalentGivenName, George]
-
A.
equivalentGivenNameInEnglish
Indicates that two given names are equivalent in meaning or usage when expressed in English.
-
B.
equivalentSurname
Indicates that two entities share the same surname or are considered to have matching surnames for identification or equivalence purposes.
-
C.
givenNameFor
Indicates that one entity is the personal first name assigned to or used for another entity.
-
D.
isEquivalentSurnameInEnglish
Indicates that two surnames are considered equivalent when rendered or transliterated into English.
-
E.
givenName
Indicates the personal first name assigned to an individual.
- F. None of above. chosen
Provenance (4 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 12:24 a.m.