Triple
T27603461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Corinthian Yacht Club |
E700114
|
entity |
| Predicate | clubhouseMaterial |
P104293
|
FINISHED |
| Object | reinforced concrete |
—
|
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: reinforced concrete | Statement: [Royal Corinthian Yacht Club, clubhouseMaterial, reinforced concrete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubhouseMaterial Context triple: [Royal Corinthian Yacht Club, clubhouseMaterial, reinforced concrete]
-
A.
clubhouseStyle
Indicates that one entity has a clubhouse characterized by a particular architectural or design style specified by the other entity.
-
B.
clubhouseCompletedIn
Indicates that the construction or development of a clubhouse was finished in a specified time or year.
-
C.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
featuresMaterialType
chosen
Indicates that an entity is characterized by or incorporates a specific type of material.
-
E.
hasSeatMaterial
Indicates that an entity’s seat is made of, or covered with, a specified material.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 2:09 p.m.