Triple
T7937205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subversion |
E184313
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Apache Subversion |
E184313
|
NE 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: Apache Subversion | Statement: [Subversion, name, Apache Subversion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Apache Subversion Context triple: [Subversion, name, Apache Subversion]
-
A.
Subversion
chosen
Subversion is a centralized version control system used to manage and track changes to source code and other files in software development projects.
-
B.
SVN
SVN is the IATA airport code for Hunter Army Airfield, a U.S. military airfield located near Savannah, Georgia.
-
C.
SVN
SVN is the three-letter ISO 3166-1 alpha-3 country code assigned to Slovenia.
-
D.
Perforce
Perforce is a centralized version control system widely used in game development and large-scale software projects for its performance and robust asset management.
-
E.
Plastic SCM
Plastic SCM is a distributed version control system designed for large-scale and game development projects, offering advanced branching, merging, and graphical tools.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aef2394819086eea1f6ab117aed |
completed | March 31, 2026, 3:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5c0a96ac819099ad30fb925eb329 |
completed | March 31, 2026, 5:30 a.m. |
Created at: March 30, 2026, 5:08 p.m.