Triple
T36480659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marybeth |
E898805
|
entity |
| Predicate | nameFormationType |
P175412
|
FINISHED |
| Object | compound name |
—
|
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: compound name | Statement: [Marybeth, nameFormationType, compound name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameFormationType Context triple: [Marybeth, nameFormationType, compound name]
-
A.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
B.
namesakeType
Indicates the specific kind or category of namesake relationship that exists between two entities (for example, one being named after the other as a person, place, event, or object).
-
C.
usesNameForm
Indicates that one entity adopts or applies a particular standardized form or variant of a name associated with another entity.
-
D.
formationType
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
-
E.
natureOfName
chosen
Indicates that the relationship specifies the type, origin, or semantic category of a given name.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.