Triple
T16600534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italic |
E403317
|
entity |
| Predicate | modernImportance |
P115817
|
FINISHED |
| Object | basis of many major world languages |
—
|
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: basis of many major world languages | Statement: [Italic, modernImportance, basis of many major world languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernImportance Context triple: [Italic, modernImportance, basis of many major world languages]
-
A.
majorImport
Indicates that one entity is a primary or significant source of imported goods or resources for another entity.
-
B.
historicalImpact
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
-
C.
modernInfluence
chosen
Indicates that one entity has a shaping or impactful effect on another within a contemporary or current context.
-
D.
resultImportance
Indicates that one entity specifies how significant, critical, or impactful the outcome or result of another entity is.
-
E.
militaryImportance
Indicates the degree to which something is strategically or operationally significant to military objectives or capabilities.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d75772c8190b02aef02ea6788e1 |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.