Triple
T27615318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CodePlex |
E700424
|
entity |
| Predicate | supportedVersionControlSystem |
P9403
|
FINISHED |
| Object | Team Foundation Server |
—
|
NE NERFINISHED |
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: Team Foundation Server | Statement: [CodePlex, supportedVersionControlSystem, Team Foundation Server]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedVersionControlSystem Context triple: [CodePlex, supportedVersionControlSystem, Team Foundation Server]
-
A.
previouslySupportedVersionControlSystem
Indicates that an entity used to support a particular version control system in the past but no longer does so.
-
B.
usesVersionControlSystem
chosen
Indicates that an entity employs a version control system to manage and track changes to its files or code.
-
C.
previousVersionControlSystem
Indicates that one version control system was used before another as its predecessor in managing revisions.
-
D.
supportsVersioning
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
-
E.
supportsGitIntegration
Indicates that one entity provides functionality or compatibility that allows integration with Git for version control operations.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: April 27, 2026, 2:12 p.m.