Triple
T25507937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belphoebe |
E639294
|
entity |
| Predicate | sharesNameEtymologyWith |
P28322
|
FINISHED |
| Object | Phoebe |
—
|
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: Phoebe | Statement: [Belphoebe, sharesNameEtymologyWith, Phoebe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesNameEtymologyWith Context triple: [Belphoebe, sharesNameEtymologyWith, Phoebe]
-
A.
sharesEtymologyWith
chosen
Indicates that two terms originate from the same linguistic root or source word, or have closely related historical word origins.
-
B.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
C.
sharesSurnameWithMany
Indicates that an entity has the same surname as a large number of other entities.
-
D.
possibleNameEtymology
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
E.
commonInOnomastics
Indicates that a name, term, or pattern frequently appears or is widely used within the study and practice of naming (onomastics).
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 21, 2026, 2:47 p.m.