Triple
T31395081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Building 20 |
E800842
|
entity |
| Predicate | hostedResearchIn |
P178626
|
FINISHED |
| Object | radar technology |
—
|
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: radar technology | Statement: [Building 20, hostedResearchIn, radar technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedResearchIn Context triple: [Building 20, hostedResearchIn, radar technology]
-
A.
supportedResearch
Indicates that one entity provided assistance, resources, or backing to enable or advance the research activities of another entity.
-
B.
coResearcher
Indicates that two or more individuals collaborate as peers on the same research work or project.
-
C.
coordinatesResearchOn
Indicates that one entity organizes and directs the planning, execution, and integration of research activities involving another entity.
-
D.
researchAccess
Indicates that one entity is permitted to access, use, or retrieve another entity specifically for research-related purposes.
-
E.
researchIntegration
Indicates the incorporation and coordination of research findings, methods, or activities into a broader system, process, or project so they function together coherently.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 29, 2026, 9:19 p.m.