Triple
T493487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altaic languages (proposed) |
E10238
|
entity |
| Predicate | stillDiscussedIn |
P5303
|
FINISHED |
| Object | historical linguistics |
—
|
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 linguistics | Statement: [Altaic languages (proposed), stillDiscussedIn, historical linguistics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stillDiscussedIn Context triple: [Altaic languages (proposed), stillDiscussedIn, historical linguistics]
-
A.
frequentlyDiscussedIn
chosen
Indicates that a topic, subject, or entity is often the focus of conversation, debate, or mention within a particular context or medium.
-
B.
influencedDiscussionOf
Indicates that one entity had an effect on the way another entity was discussed, framed, or debated.
-
C.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion with another entity.
-
D.
debatedAt
Indicates that a debate or formal discussion involving the subject took place at the specified location or event.
-
E.
notedIn
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f0fbfa408190aeb3b93996a35c00 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf90ca88190b6a182e5b6733612 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.