Triple
T6313452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newport Country Club |
E141558
|
entity |
| Predicate | clubhouseStyle |
P69998
|
FINISHED |
| Object | Beaux-Arts architecture |
—
|
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: Beaux-Arts architecture | Statement: [Newport Country Club, clubhouseStyle, Beaux-Arts architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubhouseStyle Context triple: [Newport Country Club, clubhouseStyle, Beaux-Arts architecture]
-
A.
chorusFeature
Indicates that one entity participates in or is highlighted within the chorus section of another entity, such as a song or musical piece.
-
B.
hasClubhouses
Indicates that an entity possesses, manages, or is associated with one or more clubhouses.
-
C.
chorus
Indicates that multiple entities jointly produce or participate in a coordinated vocal or expressive performance, typically as a unified group.
-
D.
chorusType
Indicates the specific kind or category of chorus associated with an entity (e.g., type of vocal ensemble or choral grouping).
-
E.
channels
Indicates that one entity serves as a medium, route, or conduit through which another entity is directed, transmitted, or delivered.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064a075dc8190acf7ec010cb4b00c |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:28 p.m.