Triple
T24400318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tran Thi Ly Bridge |
E615147
|
entity |
| Predicate | hasTypeOfIllumination |
P1280
|
FINISHED |
| Object | architectural lighting |
—
|
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: architectural lighting | Statement: [Tran Thi Ly Bridge, hasTypeOfIllumination, architectural lighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfIllumination Context triple: [Tran Thi Ly Bridge, hasTypeOfIllumination, architectural lighting]
-
A.
isIlluminatedBy
Indicates that one entity receives light from, or is lit up by, another entity.
-
B.
illuminationCondition
Indicates the lighting or brightness conditions under which an event, observation, or interaction takes place.
-
C.
hasLighting
chosen
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
D.
hasRelatedIlluminant
Indicates that one entity is associated with another entity that serves as a corresponding or contextually relevant illuminant (light source) for it.
-
E.
hasLightingEffect
Indicates that one entity applies, produces, or is associated with a particular lighting effect on another entity or environment.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294da48348190bcdcab21209deaac |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.