Triple
T34658892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | União do Vegetal |
E890052
|
entity |
| Predicate | hasMeetingPlaceType |
P199031
|
FINISHED |
| Object | temple |
—
|
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: temple | Statement: [União do Vegetal, hasMeetingPlaceType, temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeetingPlaceType Context triple: [União do Vegetal, hasMeetingPlaceType, temple]
-
A.
meetsType
Indicates that one entity encounters or comes into contact with another entity in a particular manner or context.
-
B.
hasMeetingLocation
Indicates that an entity (such as a meeting or event) takes place at or is associated with a specific location.
-
C.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
-
D.
meetsInPlaceOf
Indicates that one entity meets or comes together with another specifically at a designated place or location.
-
E.
meetingPlaceOf
Indicates the location where a particular meeting or gathering takes place or is held for the referenced entities.
- F. None of above. chosen
Provenance (4 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69ff1ba7494481908678a7a0f93dbd03 |
completed | May 9, 2026, 11:33 a.m. |
Created at: May 1, 2026, 2:04 a.m.