Triple
T721017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Picene |
E14614
|
entity |
| Predicate | researchedBy |
P1945
|
FINISHED |
| Object | historical linguists |
—
|
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: historical linguists | Statement: [North Picene, researchedBy, historical linguists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchedBy Context triple: [North Picene, researchedBy, historical linguists]
-
A.
studiedBy
chosen
Indicates that a subject (such as a field, topic, or object) is examined, researched, or learned by an agent (such as a person or group).
-
B.
researchStrength
Indicates the degree to which an entity possesses strong capabilities, performance, or impact in conducting research.
-
C.
conductsResearchAt
Indicates that a subject carries out research activities at a specified institution, organization, or location.
-
D.
involvedScientist
Indicates that a scientist participated in, contributed to, or was otherwise actively involved with a specified project, study, or activity.
-
E.
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.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58fa41c819082de2cc4e0cb2943 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f513608190b716b939d574c292 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.