Triple
T2867705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edison Laboratory |
E63478
|
entity |
| Predicate | researchModel |
P42828
|
FINISHED |
| Object | team-based invention under centralized facilities |
—
|
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: team-based invention under centralized facilities | Statement: [Edison Laboratory, researchModel, team-based invention under centralized facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchModel Context triple: [Edison Laboratory, researchModel, team-based invention under centralized facilities]
-
A.
researchUser
Indicates that an entity conducts research on, studies, or investigates a particular user.
-
B.
researchTopic
Indicates that a subject conducts or focuses research on a particular topic or area of study.
-
C.
researchArm
Indicates that an entity is a specific study group or treatment arm within a research or clinical trial design.
-
D.
researchOutcome
Indicates that an action, study, or investigation produces a specific result, finding, or conclusion.
-
E.
researchCenter
Indicates that one entity functions as a research center associated with, operated by, or focused on the other entity.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfbcebcc81909a78a1787d823e3e |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddedd72c819094a9c4161af07780 |
completed | March 7, 2026, 8:12 a.m. |
Created at: March 6, 2026, 10:02 p.m.