Triple
T38502977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Lackey |
E919889
|
entity |
| Predicate | meetsAvalynThrough |
P32020
|
FINISHED |
| Object | UFO support group |
—
|
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: UFO support group | Statement: [Brian Lackey, meetsAvalynThrough, UFO support group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsAvalynThrough Context triple: [Brian Lackey, meetsAvalynThrough, UFO support group]
-
A.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
-
B.
meetsVia
chosen
Indicates that two entities come into contact or interact with each other through a specified intermediary medium, channel, or mechanism.
-
C.
firstMeets
Indicates that one entity encounters or comes into contact with another entity for the first time.
-
D.
meetsUnder
Indicates that one entity encounters or comes together with another entity in a context where it is subordinate to, governed by, or occurring within the scope or authority of a third entity or condition.
-
E.
meets
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.