Triple
T30600725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tengwar |
E778894
|
entity |
| Predicate | hasAdditionalMarks |
P185958
|
FINISHED |
| Object | punctuation signs |
—
|
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: punctuation signs | Statement: [Tengwar, hasAdditionalMarks, punctuation signs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdditionalMarks Context triple: [Tengwar, hasAdditionalMarks, punctuation signs]
-
A.
mayHaveMarkings
Indicates that an entity is permitted or able to possess certain markings or distinguishing signs.
-
B.
hasAdditionalLetters
Indicates that one entity contains extra or more letters than another entity, beyond a specified base set or reference.
-
C.
reportedMarks
Indicates that an entity has formally communicated or submitted the marks/grades of another entity (such as a student or assessment) to a relevant party or system.
-
D.
hasProofMark
Indicates that an entity bears a specific proof mark signifying it has passed an official test or inspection.
-
E.
hasMeasurementMarkings
Indicates that one entity bears visible measurement indicators or scale markings on its surface for quantifying something.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: April 29, 2026, 8:25 p.m.