Triple
T36920694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rundown pub |
E913189
|
entity |
| Predicate | mayAttract |
P1347
|
FINISHED |
| Object | small group of regular patrons |
—
|
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: small group of regular patrons | Statement: [Rundown pub, mayAttract, small group of regular patrons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAttract Context triple: [Rundown pub, mayAttract, small group of regular patrons]
-
A.
attracts
chosen
Indicates that one entity exerts a force or influence that draws another entity toward it.
-
B.
attractedFigure
Indicates that one figure is visually or emotionally drawn toward, or finds appealing, another figure.
-
C.
succeededByAttraction
Indicates that one attraction or point of interest is directly followed or replaced by another attraction in a sequence or timeline.
-
D.
mayEngageIn
Indicates that one entity is permitted or authorized to participate in or perform a particular activity or interaction with another entity.
-
E.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fdcb96c8819084bd2a37cd383685 |
completed | May 5, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.