Triple
T32894553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | little Mary |
E841432
|
entity |
| Predicate | hasBaseName |
P74957
|
FINISHED |
| Object | Mary |
—
|
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: Mary | Statement: [little Mary, hasBaseName, Mary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseName Context triple: [little Mary, hasBaseName, Mary]
-
A.
hasGivenNameBasis
Indicates that one entity’s given name is derived from, based on, or formed using another entity (such as a name, word, or person) as its basis.
-
B.
hasBaseNameMeaning
Indicates that an entity’s base name carries or is associated with a particular meaning.
-
C.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
D.
hasRootName
chosen
Indicates that an entity is associated with a fundamental or original name from which its other names or forms are derived.
-
E.
hasBaseField
Indicates that one entity serves as the foundational or underlying field structure upon which another entity is defined or constructed.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:18 a.m.