Triple
T11325962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mianyang |
E268218
|
entity |
| Predicate | hasResearchSector |
P36094
|
FINISHED |
| Object | national defense 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: national defense technology | Statement: [Mianyang, hasResearchSector, national defense technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchSector Context triple: [Mianyang, hasResearchSector, national defense technology]
-
A.
hasResearchArea
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
-
B.
hasResearchServices
Indicates that one entity provides or offers research-related services to another entity.
-
C.
hasResearchActivities
Indicates that an entity engages in, conducts, or is associated with research-related activities.
-
D.
conductsResearchAt
Indicates that a subject carries out research activities at a specified institution, organization, or location.
-
E.
hasTypeOfResearch
chosen
Indicates that an entity is associated with a particular category or kind of research it involves or conducts.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e2253881909518cad0f12ef612 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.