Triple
T34954892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTAN |
E1008099
|
entity |
| Predicate | isPrimaryRepositoryFor |
P19959
|
FINISHED |
| Object | TeX community |
—
|
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: TeX community | Statement: [CTAN, isPrimaryRepositoryFor, TeX community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryRepositoryFor Context triple: [CTAN, isPrimaryRepositoryFor, TeX community]
-
A.
hasRepository
chosen
Indicates that an entity maintains or is associated with a specific repository (such as a code, data, or content store).
-
B.
repositoryFor
Indicates a relationship where one entity serves as a storage location or container that holds, manages, or maintains another entity.
-
C.
isSisterProjectOf
Indicates that two projects are related and aligned in purpose or scope, typically operating in parallel under a common umbrella or organization.
-
D.
isPrimary
Indicates that one entity holds the main, leading, or most important role or status in relation to another entity or within a given context.
-
E.
isMainLibraryOf
Indicates that a library serves as the primary or central library for a given organization, system, or collection.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4 p.m.