Triple
T211003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Society of Rheology |
E4717
|
entity |
| Predicate | bringsTogether |
P1139
|
FINISHED |
| Object | scientists |
—
|
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: scientists | Statement: [Society of Rheology, bringsTogether, scientists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bringsTogether Context triple: [Society of Rheology, bringsTogether, scientists]
-
A.
collectsFrom
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from another entity.
-
B.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
-
C.
meetsAs
chosen
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
-
D.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
E.
couplesTo
Indicates that one entity is joined or linked to another in a way that allows interaction, transfer, or mutual influence between them.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b4f71b88190866c8262922ae204 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.