Triple
T7423326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDF 1.1 N-Quads |
E171300
|
entity |
| Predicate | syntaxFamily |
P76886
|
FINISHED |
| Object | RDF line-based syntaxes |
—
|
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: RDF line-based syntaxes | Statement: [RDF 1.1 N-Quads, syntaxFamily, RDF line-based syntaxes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: syntaxFamily Context triple: [RDF 1.1 N-Quads, syntaxFamily, RDF line-based syntaxes]
-
A.
typeFamily
Indicates that one entity is classified as a family-related type or belongs to a family category in relation to another entity.
-
B.
patternFamily
Indicates that one entity belongs to, or is categorized within, a family or group of related patterns defined by the other entity.
-
C.
scriptFamily
Indicates that one writing system belongs to the same broader script group or classification as another.
-
D.
macroFamily
Indicates that two or more language families are hypothesized to share a common higher-level genetic origin, forming a larger proposed macro-family grouping.
-
E.
styleFamily
Indicates that one style is grouped within the same stylistic family or category as another style.
- F. None of above. chosen
Provenance (4 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2eece588190905774e7151edcb8 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1ee5ab8819091082324f2dc3b8c |
completed | March 27, 2026, 9:09 p.m. |
Created at: March 27, 2026, 3:12 p.m.