Triple
T18586706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall A |
E454252
|
entity |
| Predicate | collaborationsInvolve |
P126368
|
FINISHED |
| Object | international research groups |
—
|
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: international research groups | Statement: [Hall A, collaborationsInvolve, international research groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationsInvolve Context triple: [Hall A, collaborationsInvolve, international research groups]
-
A.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
B.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
C.
frequentlyCollaboratedWith
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
-
D.
containsCollaboration
chosen
Indicates that one entity includes or involves a collaborative relationship or joint activity with another entity.
-
E.
collaborationAt
Indicates that two or more entities are working together or jointly engaged in an activity, project, or context at a specific place, organization, or event.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b210488190ba62d3bf6e1a595c |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.