Triple
T921616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meta AI |
E19895
|
entity |
| Predicate | researchAreas |
P934
|
FINISHED |
| Object | foundation models |
—
|
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: foundation models | Statement: [Meta AI, researchAreas, foundation models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchAreas Context triple: [Meta AI, researchAreas, foundation models]
-
A.
hasResearchArea
chosen
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.
researchStrength
Indicates the degree to which an entity possesses strong capabilities, performance, or impact in conducting research.
-
C.
researchClassification
Indicates that an entity is assigned a specific category or type within a research-related classification scheme.
-
D.
researchContext
Indicates the situational, methodological, or thematic setting within which a particular piece of research is conducted or interpreted.
-
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.
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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b313cb908190ad78b3a54e4f2eb7 |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b295b02481908e5f53bfcb83cc94 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.