Triple
T18631816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People’s Living Lab |
E455435
|
entity |
| Predicate | envisionsExpoAs |
P534
|
FINISHED |
| Object | large-scale experimental space |
—
|
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: large-scale experimental space | Statement: [People’s Living Lab, envisionsExpoAs, large-scale experimental space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: envisionsExpoAs Context triple: [People’s Living Lab, envisionsExpoAs, large-scale experimental space]
-
A.
envisionedAs
chosen
Indicates that one entity is mentally pictured, imagined, or conceived in terms of another entity or role.
-
B.
exhibitFor
Indicates a relationship where something is displayed, presented, or shown for the benefit, use, or consideration of a particular audience, purpose, or entity.
-
C.
operatorDuringExpo
Indicates that an entity serves as an operator specifically during an exposition or expo event.
-
D.
expoSite
Indicates that a site or location is designated as the venue or setting for an exposition or exhibition event.
-
E.
previousExpo
Indicates that one entity is an exposition or expo event that occurred immediately before another in a temporal or sequential order.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fc4c5648190b771e9b080e98c15 |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.