Triple
T27663316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Config Sync |
E697173
|
entity |
| Predicate | configurationSourceType |
P75726
|
FINISHED |
| Object | Git |
—
|
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: Git | Statement: [Config Sync, configurationSourceType, Git]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationSourceType Context triple: [Config Sync, configurationSourceType, Git]
-
A.
carbonSource
Indicates that one entity serves as the source or provider of carbon for another entity or process.
-
B.
detectedSourceType
Indicates the type or category of source from which something was detected.
-
C.
configurationLocation
Indicates the place or context where a configuration is stored, applied, or defined.
-
D.
mainSourceType
chosen
Indicates the primary category or kind of source from which something originates or is derived.
-
E.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 2:37 p.m.