Triple
T5909751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vroegnieuwnederlands |
E131429
|
entity |
| Predicate | taalgroep |
P31853
|
FINISHED |
| Object | Germaanse talen |
—
|
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: Germaanse talen | Statement: [Vroegnieuwnederlands, taalgroep, Germaanse talen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taalgroep Context triple: [Vroegnieuwnederlands, taalgroep, Germaanse talen]
-
A.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
B.
team
Indicates that multiple entities are grouped together as a collaborative unit working toward shared goals or tasks.
-
C.
participantGroup
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
-
D.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
-
E.
linguisticSubgroup
chosen
Indicates that one linguistic group forms a subordinate or specialized subset within a larger linguistic group or family.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.