Triple
T18204852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XLM-R |
E435876
|
entity |
| Predicate | releasedByOrganizationType |
P130219
|
FINISHED |
| Object | industry research lab |
—
|
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: industry research lab | Statement: [XLM-R, releasedByOrganizationType, industry research lab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedByOrganizationType Context triple: [XLM-R, releasedByOrganizationType, industry research lab]
-
A.
releasedBy
Indicates that something (such as a product, work, or item) is made available, issued, or launched by a particular agent or organization.
-
B.
introducedByOrganization
Indicates that an entity was brought into existence, presented, or launched by a specific organization.
-
C.
releasedInsteadOf
Indicates that one entity was released in place of, or as a substitute for, another entity that was not released.
-
D.
releasedWithSupportFrom
Indicates that something was released or launched with assistance, backing, or sponsorship provided by another party.
-
E.
releasedFor
Indicates that something has been made available or authorized for public use, distribution, or access.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e222831081908f7d5500424e3acb |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:32 a.m.