Triple
T21899382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lap Dance |
E540766
|
entity |
| Predicate | hasTargetLocation |
P43296
|
FINISHED |
| Object | bar |
—
|
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: bar | Statement: [Lap Dance, hasTargetLocation, bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetLocation Context triple: [Lap Dance, hasTargetLocation, bar]
-
A.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
B.
targetLocation
chosen
Indicates the specific place or destination toward which an action, movement, or effect is directed.
-
C.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
D.
hasStageLocation
Indicates that an event, process, or staged activity occurs at or is associated with a specific location.
-
E.
hasReceiverLocation
Indicates that an entity serves as the destination or location where something is received by another party.
- 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_69e0c47b4e8c81908c8076eaa4c8e4f2 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f11fc8c2108190b55ff1ba3badc9fb |
completed | April 28, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:07 p.m.