Triple
T2889407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LaTeX |
E59582
|
entity |
| Predicate | hasDocumentClass |
P43814
|
FINISHED |
| Object | article |
—
|
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: article | Statement: [LaTeX, hasDocumentClass, article]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDocumentClass Context triple: [LaTeX, hasDocumentClass, article]
-
A.
hasDynamicalClass
Indicates that an entity belongs to a specific category defined by its dynamical or motion-related behavior (e.g., orbital or kinematic characteristics).
-
B.
hasDocumentationAt
Indicates that something is documented or described in a specific document, file, or location.
-
C.
hasServiceClass
Indicates that an entity is associated with, or categorized under, a particular class or type of service.
-
D.
hasDocumentationStatus
Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
-
E.
hasFirstDocumentedUse
Indicates that one entity is the earliest known or recorded instance in which the other entity was used or attested.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe04a68ac8190aaeafe52138beb74 |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde0f4c648190b9812e64f30c39da |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:04 p.m.