Triple
T28102762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wynn |
E710278
|
entity |
| Predicate | hasTypicalNamePosition |
P112307
|
FINISHED |
| Object | forename |
—
|
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: forename | Statement: [Wynn, hasTypicalNamePosition, forename]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalNamePosition Context triple: [Wynn, hasTypicalNamePosition, forename]
-
A.
namePosition
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
B.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
C.
typicalPositionType
chosen
Indicates the usual or most common positional role or placement type that an entity generally occupies or is associated with.
-
D.
typicalPositionsInclude
Indicates that certain positions or roles are commonly or characteristically included within something (such as an organization, structure, or context).
-
E.
typicalFullName
Indicates that the object is the standard or commonly used full name associated with the subject.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 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: April 27, 2026, 9:06 p.m.