Triple
T28900463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FreeBSD Ports Collection |
E732937
|
entity |
| Predicate | previousVersionControlSystem |
P193535
|
FINISHED |
| Object | Subversion |
—
|
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: Subversion | Statement: [FreeBSD Ports Collection, previousVersionControlSystem, Subversion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousVersionControlSystem Context triple: [FreeBSD Ports Collection, previousVersionControlSystem, Subversion]
-
A.
previouslySupportedVersionControlSystem
Indicates that an entity used to support a particular version control system in the past but no longer does so.
-
B.
usesVersionControlSystem
Indicates that an entity employs a version control system to manage and track changes to its files or code.
-
C.
previousVersionModified
Indicates that a newer version of an entity has been created by modifying the specified previous version.
-
D.
previousVersionUsedFrom
Indicates that one entity was used as the immediately preceding version from which another entity was derived or updated.
-
E.
previousVersionAdopted
Indicates that one entity has been adopted or implemented as a successor to an earlier version represented by the other entity.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: April 28, 2026, 8:02 a.m.