Triple
T4424806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arXiv |
E95183
|
entity |
| Predicate | usesVersioning |
P54501
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [arXiv, usesVersioning, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVersioning Context triple: [arXiv, usesVersioning, true]
-
A.
supportsVersioning
chosen
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
-
B.
versioningModel
Indicates that one entity serves as a versioning or revision-control model governing how versions of another entity are created, tracked, and managed.
-
C.
usesVersionControlSystem
Indicates that an entity employs a version control system to manage and track changes to its files or code.
-
D.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
E.
hasVersionCount
Indicates the total number of distinct versions associated with a given entity.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554ca5208190ba2661616dcf071c |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.