Triple
T33405411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People Wall theater |
E855424
|
entity |
| Predicate | displayContent |
P23550
|
FINISHED |
| Object | images |
—
|
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: images | Statement: [People Wall theater, displayContent, images]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displayContent Context triple: [People Wall theater, displayContent, images]
-
A.
displayState
Indicates the current visual or presentation status of an item, such as whether and how it is shown, hidden, or rendered in a user interface or display context.
-
B.
displayInterface
Indicates that one entity presents or renders a user-facing interface for another entity or process.
-
C.
displays
chosen
Indicates that one entity visually presents or shows another entity’s content or information.
-
D.
displayType
Indicates the manner or format in which something is presented, shown, or rendered.
-
E.
displayController
Indicates a relationship where one entity manages or controls the visual output or presentation of information on a display device for 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.