Triple
T32133396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamangic |
E820708
|
entity |
| Predicate | classificationDebatedBy |
P57127
|
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: [Tamangic, classificationDebatedBy, historical linguists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationDebatedBy Context triple: [Tamangic, classificationDebatedBy, historical linguists]
-
A.
debatedAs
Indicates that one entity is discussed or argued over in terms of being equivalent to, or serving in the role of, another entity within a debate or comparative argument.
-
B.
debatedWithin
chosen
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
C.
debatedBetween
Indicates a situation in which two or more parties engage in a discussion or argument over differing views about a particular issue or topic.
-
D.
hasDebateAround
Indicates that there is ongoing discussion, disagreement, or controversy surrounding the referenced entity or topic.
-
E.
fieldOfDebate
Indicates that something is the subject or domain around which a debate or argumentative discussion is centered.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 12:30 a.m.