Triple
T5020203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Llwynywermod |
E112830
|
entity |
| Predicate | notOpenAs |
P61572
|
FINISHED |
| Object | full‑time public attraction |
—
|
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: full‑time public attraction | Statement: [Llwynywermod, notOpenAs, full‑time public attraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notOpenAs Context triple: [Llwynywermod, notOpenAs, full‑time public attraction]
-
A.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
B.
notClosedUnder
Indicates that applying the operation or relation to elements of a set can produce results that do not belong to that set, so the set is not closed under that operation or relation.
-
C.
canBeOpenedBy
Indicates that one entity has the ability or permission to open another entity.
-
D.
openedWith
Indicates that an entity is opened, initiated, or accessed using a specified tool, method, or instrument.
-
E.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7342c62881909acb35849da8761c |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:36 p.m.