Triple
T246242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAS winter meeting |
E5043
|
entity |
| Predicate | attendeeType |
P6384
|
FINISHED |
| Object | professional astronomer |
—
|
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: professional astronomer | Statement: [AAS winter meeting, attendeeType, professional astronomer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attendeeType Context triple: [AAS winter meeting, attendeeType, professional astronomer]
-
A.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
B.
organizationTypeOfPresenter
Indicates that the predicate specifies the type or category of organization to which the presenter belongs or that the presenter represents.
-
C.
customerType
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
D.
engagementType
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
E.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d128c0081909908825b302ae635 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b63b0bc8190864d7324d339fb48 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.